[
https://issues.apache.org/jira/browse/CASSANDRA-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549857#comment-13549857
]
T Jake Luciani commented on CASSANDRA-4762:
-------------------------------------------
bq. maybe better option might be to just create a separate class to build
multiple names at once and use that when that make sense. It might duplicate a
bit of code but I feel that it would be cleaner overall.
Works for me
bq. On the rest of the patch:
I'll address these in the next patch
> Support multiple OR clauses for CQL3 Compact storage
> ----------------------------------------------------
>
> Key: CASSANDRA-4762
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4762
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Labels: cql3
> Fix For: 1.2.2
>
> 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 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
