[JBoss JIRA] (TEIID-4928) Couchbase - NAMEINSOURCE required for all the columns and tables
by Juraj Duráni (JIRA)
Juraj Duráni created TEIID-4928:
-----------------------------------
Summary: Couchbase - NAMEINSOURCE required for all the columns and tables
Key: TEIID-4928
URL: https://issues.jboss.org/browse/TEIID-4928
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 9.3
Reporter: Juraj Duráni
Assignee: Steven Hawkins
Option *NAMEINSOURCE* is de facto required for all the columns and tables. If it is not present then:
# column name in source query is not enclosed in back quotes - e.g. *`$cb_t1`.ShortValue* instead of *`$cb_t1`.`ShortValue`*
# name of the table is not added to the source query - e.g. *SELECT ... FROM null `$cb_t1` LET ... WHERE ...* instead of *SELECT ... FROM `smalla` `$cb_t1` LET ... WHERE ...*
This should work OOB without need to add NAMEINSOURCE option. Teiid should automatically translate column name from e.g. *MyColumn* to *`MyColumn`* if option is not set. Same with name of the table.
In case of table I think this is more serious as it does not even try name of the table but supplies *null* to the query
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4926) Couchbase - unable to retrieve data if using 'convert' in view definition
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4926?page=com.atlassian.jira.plugin... ]
Kylin Soong reassigned TEIID-4926:
----------------------------------
Assignee: Kylin Soong (was: Steven Hawkins)
> Couchbase - unable to retrieve data if using 'convert' in view definition
> -------------------------------------------------------------------------
>
> Key: TEIID-4926
> URL: https://issues.jboss.org/browse/TEIID-4926
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.3
> Reporter: Juraj Duráni
> Assignee: Kylin Soong
> Priority: Blocker
>
> I have a simple document structure in Couchbase (no nested documents, all values are strings, integers, and booleans).
> I have a source model with proper types (strings, integers, booleans) and view model defined with my target types (float, double, date,...) all with appropriate conversion.
> There are basically two issues:
> - When I try to retrieve all data from the view, Teiid ends with exception \[1\]. This is wired.
> - When I try to use explicit convert on some columns from source table (not view) it ends with similar exception \[2\].
> Additional information:
> I represent 'Null' values by excluding key from the document (nevertheless, same error occurs even if I add explicit "key":null to the definition of the document).
> \[1\]
> TEIID10076 Invalid conversion from type class java.lang.Integer with value '-24' to type class java.sql.Date
> \[2\] - case for data value
> TEIID10076 Invalid conversion from type class java.lang.Object with value '\{\}' to type class java.sql.Date
> \[3\] - Queries
> {code:sql}
> OK - select * from couchbase.smalla
> FAIL - select * from bqt1.smalla
> FAIL - select convert(datevalue, date) from couchbase.smalla
> {code}
> \[4\] VDB definition
> {code:sql}
> -- source model
> SET NAMESPACE 'http://www.teiid.org/translator/couchbase/2017' AS teiid_couchbase;
> CREATE FOREIGN TABLE SmallA (
> documentID string,
> FloatNum integer OPTIONS (NAMEINSOURCE '`smalla`.`FloatNum`'),
> IntKey integer PRIMARY KEY OPTIONS (NAMEINSOURCE '`smalla`.`IntKey`'),
> BigIntegerValue integer OPTIONS (NAMEINSOURCE '`smalla`.`BigIntegerValue`'),
> StringKey string OPTIONS (NAMEINSOURCE '`smalla`.`StringKey`'),
> CharValue string OPTIONS (NAMEINSOURCE '`smalla`.`CharValue`'),
> LongNum integer OPTIONS (NAMEINSOURCE '`smalla`.`LongNum`'),
> type string OPTIONS (NAMEINSOURCE '`smalla`.`type`'),
> DoubleNum integer OPTIONS (NAMEINSOURCE '`smalla`.`DoubleNum`'),
> ObjectValue string OPTIONS (NAMEINSOURCE '`smalla`.`ObjectValue`'),
> ShortValue integer OPTIONS (NAMEINSOURCE '`smalla`.`ShortValue`'),
> BigDecimalValue integer OPTIONS (NAMEINSOURCE '`smalla`.`BigDecimalValue`'),
> DateValue string OPTIONS (NAMEINSOURCE '`smalla`.`DateValue`'),
> BooleanValue boolean OPTIONS (NAMEINSOURCE '`smalla`.`BooleanValue`'),
> TimestampValue string OPTIONS (NAMEINSOURCE '`smalla`.`TimestampValue`'),
> ByteNum integer OPTIONS (NAMEINSOURCE '`smalla`.`ByteNum`'),
> StringNum string OPTIONS (NAMEINSOURCE '`smalla`.`StringNum`'),
> TimeValue string OPTIONS (NAMEINSOURCE '`smalla`.`TimeValue`'),
> IntNum integer OPTIONS (NAMEINSOURCE '`smalla`.`IntNum`')
> ) OPTIONS (NAMEINSOURCE '`smalla`', UPDATABLE FALSE, "teiid_couchbase:ISARRAYTABLE" 'false', "teiid_couchbase:NAMEDTYPEPAIR" '`type`:''SmallA''');
> -- view model
> CREATE VIEW SmallA (
> IntKey integer PRIMARY KEY,
> StringKey string,
> IntNum integer,
> StringNum string,
> FloatNum float,
> LongNum long,
> DoubleNum double,
> ByteNum byte,
> DateValue date,
> TimeValue time,
> TimestampValue timestamp,
> BooleanValue boolean,
> CharValue char(1),
> ShortValue short,
> BigIntegerValue biginteger,
> BigDecimalValue bigdecimal,
> ObjectValue object)
> AS
> SELECT
> IntKey, StringKey, IntNum, StringNum, convert(FloatNum, float) AS FloatNum, convert(LongNum, long) AS LongNum,
> convert(DoubleNum, double) AS DoubleNum, convert(ByteNum, byte) AS ByteNum, convert(DateValue, date) AS DateValue,
> convert(TimeValue, time) AS TimeValue, convert(TimestampValue, timestamp) AS TimstampValue, BooleanValue,
> convert(CharValue, char) AS CharValue, convert(ShortValue, short) AS ShortValue, convert(BigIntegerValue, biginteger) AS BigIntegerValue,
> convert(BigDecimalValue, bigdecimal) AS BigDecimalValue, convert(ObjectValue, object) AS ObjectValue
> FROM
> Couchbase.SmallA;
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4925) Importing a non-existing VDB gives no warning
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4925?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4925:
----------------------------------
Fix Version/s: (was: 9.2.3)
Affects Version/s: 9.2.3
> Importing a non-existing VDB gives no warning
> ---------------------------------------------
>
> Key: TEIID-4925
> URL: https://issues.jboss.org/browse/TEIID-4925
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 9.2.3
> Environment: * Wildfly 10
> * Teiid Server 9.2.3
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Attachments: ReferenceData.png
>
>
> When importing a "non-existing VDB" in a VDB, when the VDB is deployed, the VDB status is LOADING, and nothing else happens.
> Ideally a warning should be thrown in logs.
> Ex:
> <code>
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="ReferenceDataVDB" version="1">
> <description>ReferenceData VDB</description>
> <import-vdb name="NonExistingVDB" version="1"/>
>
> <model name="ReferenceData" type="VIRTUAL">
> .....
> </code>
> Logs:
> <panel>
> 12:56:11,529 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "ReferenceData-vdb.xml" (runtime-name: "ReferenceData-vdb.xml")
> 12:56:11,953 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "ReferenceData-vdb.xml" (runtime-name : "ReferenceData-vdb.xml")
> </panel>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4925) Importing a non-existing VDB gives no warning
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4925?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4925:
----------------------------------
Component/s: Server
> Importing a non-existing VDB gives no warning
> ---------------------------------------------
>
> Key: TEIID-4925
> URL: https://issues.jboss.org/browse/TEIID-4925
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Environment: * Wildfly 10
> * Teiid Server 9.2.3
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Fix For: 9.2.3
>
> Attachments: ReferenceData.png
>
>
> When importing a "non-existing VDB" in a VDB, when the VDB is deployed, the VDB status is LOADING, and nothing else happens.
> Ideally a warning should be thrown in logs.
> Ex:
> <code>
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="ReferenceDataVDB" version="1">
> <description>ReferenceData VDB</description>
> <import-vdb name="NonExistingVDB" version="1"/>
>
> <model name="ReferenceData" type="VIRTUAL">
> .....
> </code>
> Logs:
> <panel>
> 12:56:11,529 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "ReferenceData-vdb.xml" (runtime-name: "ReferenceData-vdb.xml")
> 12:56:11,953 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "ReferenceData-vdb.xml" (runtime-name : "ReferenceData-vdb.xml")
> </panel>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4925) Importing a non-existing VDB gives no warning
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4925?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-4925 at 5/22/17 7:04 PM:
----------------------------------------------------------------
The intent is to wait for that imported VDB to become available - even if it is not yet deployed. Under normal startup conditions there is no ordering to the deployment of the vdbs so there could be erroneous messages.
The best resolution would probably be to make sure there was appropriate status information available to make it clear that the vdb is waiting on other vdbs.
was (Author: shawkins):
We should add an INFO log, but the intent is to wait for that imported VDB to become available - even if it is not yet deployed.
> Importing a non-existing VDB gives no warning
> ---------------------------------------------
>
> Key: TEIID-4925
> URL: https://issues.jboss.org/browse/TEIID-4925
> Project: Teiid
> Issue Type: Enhancement
> Environment: * Wildfly 10
> * Teiid Server 9.2.3
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Fix For: 9.2.3
>
> Attachments: ReferenceData.png
>
>
> When importing a "non-existing VDB" in a VDB, when the VDB is deployed, the VDB status is LOADING, and nothing else happens.
> Ideally a warning should be thrown in logs.
> Ex:
> <code>
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="ReferenceDataVDB" version="1">
> <description>ReferenceData VDB</description>
> <import-vdb name="NonExistingVDB" version="1"/>
>
> <model name="ReferenceData" type="VIRTUAL">
> .....
> </code>
> Logs:
> <panel>
> 12:56:11,529 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "ReferenceData-vdb.xml" (runtime-name: "ReferenceData-vdb.xml")
> 12:56:11,953 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "ReferenceData-vdb.xml" (runtime-name : "ReferenceData-vdb.xml")
> </panel>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4927) Update dockerfile
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4927?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4927.
-----------------------------------
Fix Version/s: 9.3
9.1.5
9.2.4
Resolution: Done
Updated to java 8 and added a env parameter. We will separately address the minishift issue.
> Update dockerfile
> -----------------
>
> Key: TEIID-4927
> URL: https://issues.jboss.org/browse/TEIID-4927
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.3, 9.1.5, 9.2.4
>
>
> The dockerfile needs updated to java 8. It also appears to have issues running in minishift beyond the jdk version - such as:
> java.lang.IllegalStateException: WFLYSRV0124: Could not create server data directory: /opt/jboss/teiid-9.3.0.Beta3-SNAPSHOT/standalone/data
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4927) Update dockerfile
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4927?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4927:
---------------------------------------
Since the same exception initially happens even with just the WildFly image, that is a broader minishift issue.
Just the jdk change is enough for the image to run in docker.
> Update dockerfile
> -----------------
>
> Key: TEIID-4927
> URL: https://issues.jboss.org/browse/TEIID-4927
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> The dockerfile needs updated to java 8. It also appears to have issues running in minishift beyond the jdk version - such as:
> java.lang.IllegalStateException: WFLYSRV0124: Could not create server data directory: /opt/jboss/teiid-9.3.0.Beta3-SNAPSHOT/standalone/data
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (TEIID-4927) Update dockerfile
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4927:
-------------------------------------
Summary: Update dockerfile
Key: TEIID-4927
URL: https://issues.jboss.org/browse/TEIID-4927
Project: Teiid
Issue Type: Bug
Components: Build/Kits
Reporter: Steven Hawkins
Assignee: Steven Hawkins
The dockerfile needs updated to java 8. It also appears to have issues running in minishift beyond the jdk version - such as:
java.lang.IllegalStateException: WFLYSRV0124: Could not create server data directory: /opt/jboss/teiid-9.3.0.Beta3-SNAPSHOT/standalone/data
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months