You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (JIRA)" <ji...@apache.org> on 2014/09/03 10:19:52 UTC
[jira] [Comment Edited] (CASSANDRA-4762) Support IN clause for any
clustering column
[ https://issues.apache.org/jira/browse/CASSANDRA-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119525#comment-14119525 ]
Benjamin Lerer edited comment on CASSANDRA-4762 at 9/3/14 8:18 AM:
-------------------------------------------------------------------
I will cancel this patch and make another one for the 2.1.1
was (Author: blerer):
I will cancel this patch and make another one for the 2.1.X.
> 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: 2.1.1
>
> 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)