[
https://issues.apache.org/jira/browse/CASSANDRA-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172630#comment-14172630
]
Constance Eustace commented on CASSANDRA-4762:
----------------------------------------------
Ok, thanks. I can use a different schema, and maybe try out the new one. I'm
pretty interested in Presto / Shark adhoc queries, that's the main motivation
of the reengineer... this ticket is for supporting our main lookup use cases...
> Support IN clause for any clustering column
> -------------------------------------------
>
> Key: CASSANDRA-4762
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4762
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: T Jake Luciani
> Assignee: Benjamin Lerer
> Labels: cql, docs
> Fix For: 3.0
>
> Attachments: 4762-1.txt
>
>
> Given CASSANDRA-3885
> It seems it should be possible to store multiple ranges for many predicates
> even the inner parts of a composite column.
> They could be expressed as a expanded set of filter queries.
> example:
> {code}
> CREATE TABLE test (
> name text,
> tdate timestamp,
> tdate2 timestamp,
> tdate3 timestamp,
> num double,
> PRIMARY KEY(name,tdate,tdate2,tdate3)
> ) WITH COMPACT STORAGE;
> SELECT * FROM test WHERE
> name IN ('a','b') and
> tdate IN ('2010-01-01','2011-01-01') and
> tdate2 IN ('2010-01-01','2011-01-01') and
> tdate3 IN ('2010-01-01','2011-01-01')
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
