You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Semeria (JIRA)" <ji...@apache.org> on 2013/08/22 14:30:52 UTC
[jira] [Updated] (CASSANDRA-5920) Allow secondary indexed columns
to be used with IN operator
[ https://issues.apache.org/jira/browse/CASSANDRA-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Semeria updated CASSANDRA-5920:
-------------------------------------
Description:
Related to https://issues.apache.org/jira/browse/CASSANDRA-4709
Currently we get: Cannot use IN operator on column not part of the PRIMARY KEY
But with any other than the first element of a composite primary key we get: PRIMARY KEY part [COLUMN] cannot be restricted by IN relation
This is a pity, because one of the main attractions of CQL over the thrift API is the ability to do OR filtering on the node rather than the client
was:
Related to https://issues.apache.org/jira/browse/CASSANDRA-4709
Currently we get: Cannot use IN operator on column not part of the PRIMARY KEY
But with composite primary keys we get: PRIMARY KEY part [COLUMN] cannot be restricted by IN relation
This is a pity, because one of the main attractions of CQL over the thrift API is the ability to do OR filtering on the node rather than the client
> Allow secondary indexed columns to be used with IN operator
> -----------------------------------------------------------
>
> Key: CASSANDRA-5920
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5920
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: David Semeria
>
> Related to https://issues.apache.org/jira/browse/CASSANDRA-4709
> Currently we get: Cannot use IN operator on column not part of the PRIMARY KEY
> But with any other than the first element of a composite primary key we get: PRIMARY KEY part [COLUMN] cannot be restricted by IN relation
> This is a pity, because one of the main attractions of CQL over the thrift API is the ability to do OR filtering on the node rather than the client
--
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