[JBoss JIRA] (TEIID-3376) SQL Server 2008/2012 - incompatible data types in comparison after cast/convert
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3376?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3376.
---------------------------------
> SQL Server 2008/2012 - incompatible data types in comparison after cast/convert
> -------------------------------------------------------------------------------
>
> Key: TEIID-3376
> URL: https://issues.jboss.org/browse/TEIID-3376
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Environment: OS: fedora 20
> java: oracle 1.7
> arch: x86_64
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> If user want to cast/convert timestamp-value to time and then use it in comparison, Teiid throws an Exception:
> "SQLServerException: The data types datetime and time are incompatible in the greater than operator."
> Expected behavior:
> The query should return correct result as the SQL Server is able to handle similar queries (teiid does not have any problem with same query with oracle, postgres, mysql,...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3058) Cassandra: cannot compare timestamp field in where clause
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3058?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3058.
---------------------------------
> Cassandra: cannot compare timestamp field in where clause
> ----------------------------------------------------------
>
> Key: TEIID-3058
> URL: https://issues.jboss.org/browse/TEIID-3058
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7
> Environment: Cassandra with Teiid 8.7
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.9, 8.11
>
>
> It seems like Teiid is having problem to compare translate CQL if there is timestamp comparison in where clause:
> ORIGINAL SQL:
> select "cassandrads_sales"."product_family" as "cassandrads_sales_product_family",
> "cassandrads_sales"."product_family" as "cassandrads_sales_product_family1"
> from "cassandrads"."sales" "cassandrads_sales"
> where "cassandrads_sales"."the_date" <= '2013-05-01 00:00:00'
> limit 1000
> TRANSLATED CQL:
> SELECT cassandrads.sales.product_family FROM cassandrads.sales WHERE cassandrads.sales.the_date <= {ts'2013-05-01 00:00:00.0'} LIMIT 1000
> And I got this error:
> Caused by: org.teiid.translator.TranslatorException: line 1:55 no viable alternative at input '2013-05-01 00:00:0
> at org.teiid.translator.cassandra.CassandraQueryExecution.execute(CassandraQueryExecution.java:80)
> at org.teiid.translator.cassandra.CassandraQueryExecution.execute(CassandraQueryExecution.java:72)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:325)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298)
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:135)
> If it is not possible to do time/ data comparison for CQL, maybe you guys should consider to do it in memory instead. Thanks.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3400) Oracle connection not consistently usable after cancel
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3400?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3400.
---------------------------------
> Oracle connection not consistently usable after cancel
> ------------------------------------------------------
>
> Key: TEIID-3400
> URL: https://issues.jboss.org/browse/TEIID-3400
> Project: Teiid
> Issue Type: Quality Risk
> Components: Misc. Connectors
> Affects Versions: 8.10
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.10.1, 8.11
>
>
> With TEIID-3275 we made use of cancel calls more to ensure that cleanup was happening as quickly as possible. However Oracle JDBC has a bug (independently reproducible outside Teiid) where if the cancelled statement does not reach the point of thrown an exception related to the cancel, then the next statement from that connection will throw the exception.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months