April 2015 - teiid-issues - Jboss List Archives

[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 resolved TEIID-3058. ----------------------------------- Resolution: Done > 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.11, 8.9 > > > 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.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3354) AdminConsole fails getting mat view info with data roles

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3354?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3354. ----------------------------------- Resolution: Done Updated the admin executeQuery to set the work context admin flag. > AdminConsole fails getting mat view info with data roles > -------------------------------------------------------- > > Key: TEIID-3354 > URL: https://issues.jboss.org/browse/TEIID-3354 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Once data roles are enable the web console fails to get the mat view info - unless the user allows access to systemadmin for the admin user. > I'm logging this initially against the Teiid side as depending on the resolution we may want to change the admin code (for example using a SYS.table). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3354) AdminConsole fails getting mat view info with data roles

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3354?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3354: ---------------------------------- Affects Version/s: 8.7 > AdminConsole fails getting mat view info with data roles > -------------------------------------------------------- > > Key: TEIID-3354 > URL: https://issues.jboss.org/browse/TEIID-3354 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Once data roles are enable the web console fails to get the mat view info - unless the user allows access to systemadmin for the admin user. > I'm logging this initially against the Teiid side as depending on the resolution we may want to change the admin code (for example using a SYS.table). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3354) AdminConsole fails getting mat view info with data roles

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3354?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3354: --------------------------------------- Looking at this again we have the same issue the MaterializationManagers - if for any reason roles prohibit access to the views/materialization tables, then the management queries will fail. One fix would be to mark the workcontext executing queries through DQPCore.executeQuery as admin to by-pass the authorization checks. However that would mean that anyone connecting over the management interface could execute any query. That seems allowable though since someone allowed to connect would also be able to deploy any vdb they wanted as well. > AdminConsole fails getting mat view info with data roles > -------------------------------------------------------- > > Key: TEIID-3354 > URL: https://issues.jboss.org/browse/TEIID-3354 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Once data roles are enable the web console fails to get the mat view info - unless the user allows access to systemadmin for the admin user. > I'm logging this initially against the Teiid side as depending on the resolution we may want to change the admin code (for example using a SYS.table). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[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 resolved TEIID-3400. ----------------------------------- Resolution: Done Seems to be a viable solution, marking as resolved and will make available in 8.10.1. > 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.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1942) Add the support for accessing Coherence

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1942?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1942: ---------------------------------- Fix Version/s: 8.11 > Add the support for accessing Coherence > --------------------------------------- > > Key: TEIID-1942 > URL: https://issues.jboss.org/browse/TEIID-1942 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.10 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.11 > > > Add the support for using the Coherence -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[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 commented on TEIID-3058: --------------------------------------- Went ahead and switched 8.11 to use the long literal instead. Pending your feedback it looks like the 8.7.1 and 8.9 fix are sufficient for some versions of Cassandra. > 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.3.11#6341)

9 years, 8 months

1
0
0 / 0

[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 updated TEIID-3058: ---------------------------------- Fix Version/s: 8.11 > 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.3.11#6341)

9 years, 8 months

1
0
0 / 0

[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 updated TEIID-3058: ---------------------------------- Affects Version/s: (was: 8.10) > 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.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3412) Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3412?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3412: ----------------------------------- Assignee: Kylin Soong (was: Steven Hawkins) > Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8 > ------------------------------------------------------------------------------ > > Key: TEIID-3412 > URL: https://issues.jboss.org/browse/TEIID-3412 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Kylin Soong > > In JDK 1.8, the ODBC-JDBC bridge is removed, so accessing MS Access using this method will not be available. An alternative, open source, driver that can be used is: http://jackcess.sourceforge.net > In nexus: > <dependency> > <groupId>com.healthmarketscience.jackcess</groupId> > <artifactId>jackcess</artifactId> > <version>2.0.9</version> > </dependency> > This may require a new translator, but won't be know until a deeper look is done. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2015