[JBoss JIRA] (TEIID-3722) Add an option to not widen comparisons to string
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3722?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3722:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1460324|https://bugzilla.redhat.com/show_bug.cgi?id=1460324] from ASSIGNED to ON_QA
> Add an option to not widen comparisons to string
> ------------------------------------------------
>
> Key: TEIID-3722
> URL: https://issues.jboss.org/browse/TEIID-3722
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> Our resolving logic considers anything with an implicit conversion to string to be a valid widening conversion in a comparison. For example:
> int_col = '1a'
> will effectively become cast(int_col as string) = '1a'
> Or with timestamps:
> timestamp_col = '1970-01-01'
> becomes cast(timestamp_col as string) = '1970-01-01'
> In equality cases the optimizer will infer that the predicate is simply false, but when used with greater/less than comparison we'll still attempt the query with the widening conversion.
> This is most likely not the intent of the user. It would be best to provide an option that would allow an exception to be thrown rather than assuming a query that may not match the user's expectations.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (TEIID-4976) criteria duplicated when criteria includes the same columns as dependent join criteria
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4976?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4976:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1468368, https://bugzilla.redhat.com/show_bug.cgi?id=1466507
Bugzilla Update: Perform
> criteria duplicated when criteria includes the same columns as dependent join criteria
> --------------------------------------------------------------------------------------
>
> Key: TEIID-4976
> URL: https://issues.jboss.org/browse/TEIID-4976
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7.11.6_2
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
> Fix For: 10.0, 8.12.x-6.4, 8.12.12.6_3, 8.7.13.6_2
>
>
> Submitting a query that uses the same column for the join condition and criteria results in the criteria being duplicated on the dependent side of the join.
> For example:
> SELECT * FROM A, B
> WHERE B.id = A.id AND A.id IN ('1','2','3') OPTION MAKEDEP B;
> Results in the dependent side query looking like:
> SELECT ... FROM B WHERE B.id IN ('1','2','3') AND B.id IN ('1','2','3');
> This looks to have already been resolved in later versions, but I was not able to find the original JIRA that would have addressed this issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (TEIID-4983) Couchbase tests rely on unpredictable order
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4983:
-------------------------------------
Summary: Couchbase tests rely on unpredictable order
Key: TEIID-4983
URL: https://issues.jboss.org/browse/TEIID-4983
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.0, 8.12.x-6.4
The insert tests and others have metadata built off of json which depending upon the jre may return elements in a different order.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (TEIID-4957) Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIID-4957?page=com.atlassian.jira.plugin... ]
Debbie Steigner commented on TEIID-4957:
----------------------------------------
[~van.halbert] You cannot use the User Properties because it writes to the vdb.xml as <property name="connection-type" value="NONE"/> and it needs to be <connection-type>NONE</connection-type>
I already logged that bug as https://issues.jboss.org/browse/TEIIDDES-3087
> Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart
> -------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4957
> URL: https://issues.jboss.org/browse/TEIID-4957
> Project: Teiid
> Issue Type: Bug
> Components: VDB
> Affects Versions: 8.12.10.6_3
> Reporter: Debbie Steigner
> Assignee: Ramesh Reddy
> Fix For: 10.0
>
>
> After deploying a VDB to a managed server group, set the Connection type to anything but the default of By_Version, so None or Any. Now restart the server and you'll see the Connection type is reset to the default.
> What I see is that when the change is made a vdb.xml with that new connection-type is written to the /DVserverhome/domain/servers/server-two/data/teiid-data/SampleVDB_1 folder, this folder is deleted upon a restart though so the change is not kept.
> This only happens in Domain mode, running in Standalone mode saves the change because the teiid-data is not deleted on a restart.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (TEIID-4928) Couchbase - NAMEINSOURCE required for all the columns and tables
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4928?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4928:
----------------------------------
Fix Version/s: 9.3
> 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: Kylin Soong
> Fix For: 9.3
>
>
> 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)
6 years, 11 months
[JBoss JIRA] (TEIID-4967) Couchbase - incorrect data returned from VIEW if one value is NULL
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4967?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4967.
-----------------------------------
Resolution: Done
> Couchbase - incorrect data returned from VIEW if one value is NULL
> ------------------------------------------------------------------
>
> Key: TEIID-4967
> URL: https://issues.jboss.org/browse/TEIID-4967
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 10.0, 8.12.x-6.4, 9.3.1
>
>
> I have a source model with FOREIGN TABLE and view model with VIEW which extracts subset of columns defined in FOREIGN TABLE.
> If one value in document is missing (i.e. from Teiid's point of view it's NULL), Teiid returns incorrect data from VIEW.
> In some cases, it returns NULL values for multiple columns (even if there is only one column with NULL).
> In other cases it shifts values - value from column c contains value of column c+1, column c+1 contains value of c+2 etc.
> For Source model, I tried both NATIVE and DDL metadata.
> If you need, I can provide you access to testing environment.
> *Query:* SELECT * FROM couchbase_small.smalla WHERE intkey = 5;
> *Result*
> ||documentID||FloatNum||IntKey||BigIntegerValue||StringKey||CharValue||LongNum||type||DoubleNum||ObjectValue||ShortValue||BigDecimalValue||DateValue||BooleanValue||TimestampValue||ByteNum||StringNum||TimeValue||IntNum||
> |smalla_5|-19|5|-19|5|0|-19|SmallA|-19|-19|-32763|-19|2000-01-06|true|2000-01-01 00:00:05.0|<null>|-19|05:00:00|-19|
> *Query:* SELECT * FROM bqt1.smalla WHERE intkey = 5;
> *Result:*
> ||IntKey||StringKey||IntNum||StringNum||FloatNum||LongNum||DoubleNum||ByteNum||DateValue||TimeValue||TimestampValue||BooleanValue||CharValue||ShortValue||BigIntegerValue||BigDecimalValue||ObjectValue||
> |5|5|-19|-19|-19|-19|-19|<null>|<null>|<null>|<null>|true|<null>|<null>|<null>|<null>|<null>|
> *Query:* SELECT * FROM bqt1.smalla WHERE intkey = 0;
> *Result:* Error: TEIID10074 Invalid Byte format in String: 2000-01-01
> *Stack trace:*
> {code:plain}
> 12:55:05,263 WARN [org.teiid.CONNECTOR] (Worker15_QueryProcessorQueue279) Connector worker process failed for atomic-request=5x16wQN8Jjck.15.0.61: org.teiid.core.types.TransformationException: TEIID10074 Invalid Byte format in String: 2000-01-01
> at org.teiid.core.types.basic.StringToByteTransform.transformDirect(StringToByteTransform.java:43) [teiid-common-core-8.12.11.6_4-redhat-64-4.jar:8.12.11.6_4-redhat-64-4]
> at org.teiid.core.types.Transform.transform(Transform.java:47) [teiid-common-core-8.12.11.6_4-redhat-64-4.jar:8.12.11.6_4-redhat-64-4]
> at org.teiid.core.types.DataTypeManager.transformValue(DataTypeManager.java:942) [teiid-common-core-8.12.11.6_4-redhat-64-4.jar:8.12.11.6_4-redhat-64-4]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.correctTypes(ConnectorWorkItem.java:593)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:446)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:236)
> at sun.reflect.GeneratedMethodAccessor88.invoke(Unknown Source) [:1.8.0-internal]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0-internal]
> at java.lang.reflect.Method.invoke(Method.java:483) [rt.jar:1.8.0-internal]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy45.more(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0-internal]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0-internal]
> {code}
> *Query:* SELECT IntKey, IntNum, FloatNum FROM Couchbase_small.SmallA
> *Result:*
> ||IntKey||IntNum||FloatNum||
> |0|<null>|-24|
> |1|-23|-23|
> |10|-14|-14|
> |...|...|...|
> *Query:* SELECT IntKey, IntNum, FloatNum FROM BQT1.SmallA
> *Result:*
> ||IntKey||IntNum||FloatNum||
> |0|-24|<null>|
> |1|-23|-23|
> |10|-14|-14|
> |...|...|...|
> {code:xml|title=VDB}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="couchbase" version="1">
> <model name="Couchbase_small" type="PHYSICAL" visible="false">
> <source name="couchbase_small" connection-jndi-name="java:/couchbase_small" translator-name="couchbase"/>
> <metadata type="DDL">
> SET NAMESPACE 'http://www.teiid.org/translator/couchbase/2017' AS teiid_couchbase;
> CREATE FOREIGN TABLE SmallA (
> documentID string,
> FloatNum integer OPTIONS (NAMEINSOURCE '`FloatNum`'),
> IntKey integer PRIMARY KEY OPTIONS (NAMEINSOURCE '`IntKey`'),
> BigIntegerValue integer OPTIONS (NAMEINSOURCE '`BigIntegerValue`'),
> StringKey string OPTIONS (NAMEINSOURCE '`StringKey`'),
> CharValue string OPTIONS (NAMEINSOURCE '`CharValue`'),
> LongNum integer OPTIONS (NAMEINSOURCE '`LongNum`'),
> type string OPTIONS (NAMEINSOURCE '`type`'),
> DoubleNum integer OPTIONS (NAMEINSOURCE '`DoubleNum`'),
> ObjectValue string OPTIONS (NAMEINSOURCE '`ObjectValue`'),
> ShortValue integer OPTIONS (NAMEINSOURCE '`ShortValue`'),
> BigDecimalValue integer OPTIONS (NAMEINSOURCE '`BigDecimalValue`'),
> DateValue string OPTIONS (NAMEINSOURCE '`DateValue`'),
> BooleanValue boolean OPTIONS (NAMEINSOURCE '`BooleanValue`'),
> TimestampValue string OPTIONS (NAMEINSOURCE '`TimestampValue`'),
> ByteNum integer OPTIONS (NAMEINSOURCE '`ByteNum`'),
> StringNum string OPTIONS (NAMEINSOURCE '`StringNum`'),
> TimeValue string OPTIONS (NAMEINSOURCE '`TimeValue`'),
> IntNum integer OPTIONS (NAMEINSOURCE '`IntNum`')
> ) OPTIONS (NAMEINSOURCE '`dvqe_small`', UPDATABLE FALSE, "teiid_couchbase:ISARRAYTABLE" 'false', "teiid_couchbase:NAMEDTYPEPAIR" '`type`:''SmallA''');
> </metadata>
> </model>
> <model name="BQT1" type="VIRTUAL">
> <metadata type="DDL">
> 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 TimestampValue, 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_small.SmallA;
> </metadata>
> </model>
> </vdb>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (TEIID-4972) Couchbase - query with comparison criteria not properly translated
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4972?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4972.
-----------------------------------
Resolution: Done
> Couchbase - query with comparison criteria not properly translated
> ------------------------------------------------------------------
>
> Key: TEIID-4972
> URL: https://issues.jboss.org/browse/TEIID-4972
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 10.0, 8.12.x-6.4, 9.3.1
>
>
> Issuing simple query with comparison criteria like \[1\] returns empty result. From what I can see, the query is not properly translated - it is translated to query with syntax error \[2\].
> Another issue here which I can see is that Teiid does not provide any information to the user that query actually failed. Only empty result is returned. This one, I will report it as a separate issue.
> {code:sql|title=\[1\] Query}
> SELECT BQT1.SmallA.FloatNum FROM BQT1.SmallA WHERE BQT1.SmallA.FloatNum = 7
> {code}
> {code:plain|title=\[2\] Source-specific query}
> 10:16:09,749 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue86) TEIID29001 Source-specific Query: SELECT TONUMBER(`$cb_c1_FloatNum`) FROM `dvqe_small` `$cb_t1` LET `$cb_c1_FloatNum` = `$cb_t1`.`FloatNum`TONUMBER() WHERE TONUMBER(`$cb_c1_FloatNum`) = 7.0 AND `$cb_t1`.`type` = 'SmallA'
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months