[
https://issues.apache.org/jira/browse/CASSANDRA-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14903240#comment-14903240
]
Benjamin Lerer edited comment on CASSANDRA-4386 at 9/22/15 7:40 PM:
--------------------------------------------------------------------
The main problem with adding support for {{IN}}, {{>}}, {{>=}}, {{<=}} or {{<}}
is with ordering.
The primary keys are sorted per index entry so if multiple index entries are
read we lose the ordering.
As it is not possible to sort the rows in memory if we implements that feature
the rows will probably be returned unordered.
was (Author: blerer):
The main problem with adding support for {{IN}}, {{>}}, {{>=}}, {{<=}} or {{<}}
is with ordering.
The primary keys are sorted per index entry so if multiple index entries are
read we lose the ordering.
One of the option will be to re
> Allow cql to use the IN syntax on secondary index values
> --------------------------------------------------------
>
> Key: CASSANDRA-4386
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4386
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jeremy Hanna
> Assignee: Benjamin Lerer
> Priority: Minor
> Labels: cql
>
> Currently CQL has a syntax for using IN to get a set of rows with a set of
> keys. This would also be very helpful for use with columns with secondary
> indexes on them. Such as:
> {code}
> select * from users where first_name in ('françois','frank');
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
