[JBoss JIRA] (TEIID-2724) Suggestion for Cassandra: implement fallback plan if push-down CQL fails
by Ivan Chan (JIRA)
[ https://issues.jboss.org/browse/TEIID-2724?page=com.atlassian.jira.plugin... ]
Ivan Chan updated TEIID-2724:
-----------------------------
Summary: Suggestion for Cassandra: implement fallback plan if push-down CQL fails (was: Suggestion for Cassandra: implement fallback plan for push-down CQL fails)
> Suggestion for Cassandra: implement fallback plan if push-down CQL fails
> -------------------------------------------------------------------------
>
> Key: TEIID-2724
> URL: https://issues.jboss.org/browse/TEIID-2724
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Teiid 8.6 with Cassandra
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Labels: teiid
>
> Sometimes push down sql doesn't work in Cassandra database because most of the time filtering only works on petition key or index column. For example, it won't be possible to apply "IN" clause on non-petition key column. Therefore, I suggest if push down sql fails to execute, I would like to see Teiid to the filtering using Teiid in-memory engine. Thanks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (TEIID-2724) Suggestion for Cassandra
by Ivan Chan (JIRA)
Ivan Chan created TEIID-2724:
--------------------------------
Summary: Suggestion for Cassandra
Key: TEIID-2724
URL: https://issues.jboss.org/browse/TEIID-2724
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.6
Environment: Teiid 8.6 with Cassandra
Reporter: Ivan Chan
Assignee: Steven Hawkins
Sometimes push down sql doesn't work in Cassandra database because most of the time filtering only works on petition key or index column. For example, it won't be possible to apply "IN" clause on non-petition key column. Therefore, I suggest if push down sql fails to execute, I would like to see Teiid to the filtering using Teiid in-memory engine. Thanks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (TEIID-2724) Suggestion for Cassandra: implement fallback plan for push-down CQL fails
by Ivan Chan (JIRA)
[ https://issues.jboss.org/browse/TEIID-2724?page=com.atlassian.jira.plugin... ]
Ivan Chan updated TEIID-2724:
-----------------------------
Summary: Suggestion for Cassandra: implement fallback plan for push-down CQL fails (was: Suggestion for Cassandra)
> Suggestion for Cassandra: implement fallback plan for push-down CQL fails
> --------------------------------------------------------------------------
>
> Key: TEIID-2724
> URL: https://issues.jboss.org/browse/TEIID-2724
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Teiid 8.6 with Cassandra
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Labels: teiid
>
> Sometimes push down sql doesn't work in Cassandra database because most of the time filtering only works on petition key or index column. For example, it won't be possible to apply "IN" clause on non-petition key column. Therefore, I suggest if push down sql fails to execute, I would like to see Teiid to the filtering using Teiid in-memory engine. Thanks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (TEIID-2722) Cassandra: ORDER BY should do it in memory instead of trying to push down Cassandra in some cases
by Ivan Chan (JIRA)
Ivan Chan created TEIID-2722:
--------------------------------
Summary: Cassandra: ORDER BY should do it in memory instead of trying to push down Cassandra in some cases
Key: TEIID-2722
URL: https://issues.jboss.org/browse/TEIID-2722
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.6
Environment: Teiid 8.6 Alpha with Cassandra 1.2.11
Reporter: Ivan Chan
Assignee: Steven Hawkins
When I tried to join 2 tables together from same keyspace using Teiid 8.6 Alpha with Cassandra 1.2.11. It broke down SQL into 2 CQLs. However, teiid SQL transformer adds order by clause to the CQL which is not supported.
Original SQL:
select "cassandraDS_users"."user_id" as "cassandraDS_users_user_id",
"cassandraDS_invoice"."sale" as "cassandraDS_invoice_sale"
from "cassandraDS"."invoice" "cassandraDS_invoice"
inner join "cassandraDS"."users" "cassandraDS_users" on ("cassandraDS_invoice"."user_id" = "cassandraDS_users"."user_id")
Break Down CQL:
SELECT cassandraDS.invoice.user_id, cassandraDS.invoice.sale FROM cassandraDS.i
nvoice ORDER BY cassandraDS.invoice.user_id
SELECT cassandraDS.users.user_id FROM cassandraDS.users ORDER BY cassandraDS.us
ers.user_id
Error from CQL Driver:
com.datastax.driver.core.exceptions.InvalidQueryException: ORDER BY is only supported when the partition key is restricted by an EQ or an IN.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (TEIID-2714) Buffer defrag not working
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2714?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2714.
-----------------------------------
Resolution: Done
Made further refinements to delay unnecessary defrag and to do a targeted truncation/defrag when memory is exhausted.
> Buffer defrag not working
> -------------------------
>
> Key: TEIID-2714
> URL: https://issues.jboss.org/browse/TEIID-2714
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.6
>
>
> The defrag task is not working as expected because the header values are written by an object output stream - and not as standalone values into the block data.
> For most data usage patterns this isn't an issue as the storage files are self compacting over time due to low block assignments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (TEIID-2721) Resolving an aliased view prevents inherent update from working
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2721?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2721:
----------------------------------
Fix Version/s: 8.4.1
> Resolving an aliased view prevents inherent update from working
> ---------------------------------------------------------------
>
> Key: TEIID-2721
> URL: https://issues.jboss.org/browse/TEIID-2721
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.4.1, 8.6
>
> Attachments: 2721-77x.patch
>
>
> If an aliased form of an inherently updatable view is resolved first, we will cache invalid update info which prevents inherent insert/update from functioning correctly.
> For example with the view gx, first running:
> select * from gx as x
>
> will prevent an inherent insert such as:
> insert into gx (e1, e2, e3, e4) select * from pm1.g1
> from working as expected
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (TEIID-2718) NPE During OData Access
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2718?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2718:
-------------------------------------
Added to 8.4.x branch, due to some commit issues, I had to redo changes manually https://github.com/teiid/teiid/commit/3eb27ec89e8b8ba20613209b20b7d2549fa...
I did not include the classpath and integration test from TEIID-2717 in this commit as it working fine there.
> NPE During OData Access
> -----------------------
>
> Key: TEIID-2718
> URL: https://issues.jboss.org/browse/TEIID-2718
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.4.1, 8.6
>
>
> While issuing a query like
> {code}
> http://localhost:8080/odata/{vdb-name}.1/SYS.Properties
> {code}
> it resulted in
> {code}
> 12:07:38,308 ERROR [org.teiid.ODATA] (http-/127.0.0.1:8080-2) null TEIID16013 Error occured producing OData result.: java.lang.NullPointerException
> at org.teiid.odata.ODataSQLBuilder.selectString(ODataSQLBuilder.java:210) [classes:]
> at org.teiid.odata.TeiidProducer.getNavProperty(TeiidProducer.java:86) [classes:]
> at org.teiid.odata.TeiidProducer.getEntities(TeiidProducer.java:79) [classes:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntitiesImpl(EntitiesRequestResource.java:371) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntities(EntitiesRequestResource.java:266) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_35]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_35]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_35]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_35]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-red
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (TEIID-2718) NPE During OData Access
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2718?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2718:
---------------------------------------
Should this be included in 8.4.x?
> NPE During OData Access
> -----------------------
>
> Key: TEIID-2718
> URL: https://issues.jboss.org/browse/TEIID-2718
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.4.1, 8.6
>
>
> While issuing a query like
> {code}
> http://localhost:8080/odata/{vdb-name}.1/SYS.Properties
> {code}
> it resulted in
> {code}
> 12:07:38,308 ERROR [org.teiid.ODATA] (http-/127.0.0.1:8080-2) null TEIID16013 Error occured producing OData result.: java.lang.NullPointerException
> at org.teiid.odata.ODataSQLBuilder.selectString(ODataSQLBuilder.java:210) [classes:]
> at org.teiid.odata.TeiidProducer.getNavProperty(TeiidProducer.java:86) [classes:]
> at org.teiid.odata.TeiidProducer.getEntities(TeiidProducer.java:79) [classes:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntitiesImpl(EntitiesRequestResource.java:371) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.getEntities(EntitiesRequestResource.java:266) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_35]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_35]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_35]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_35]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-red
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months