[
https://issues.jboss.org/browse/TEIID-2722?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIID-2722.
---------------------------------
Cassandra only supports the ORDER By clause when a key is
- used in the compoiste index key as second column (partition key)
- Then the query has criteria with IN or EQ
Took SteveH suggestion and turned the ORDER By completely off.
So far my impression is Cassandra's CQL access seems to be very primitive, their
original access was based on Thrift clients. If Teiid needs any greater push down (before
CQL steps up provides the functionality) we may to look into Thrift based access.
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: Ramesh Reddy
Labels: Beta2
Fix For: 8.6
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