cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-4762) Support IN clause for any clustering column
Date Wed, 17 Sep 2014 12:51:34 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137152#comment-14137152
] 

Benjamin Lerer edited comment on CASSANDRA-4762 at 9/17/14 12:50 PM:
---------------------------------------------------------------------

Pushed the fix to [branch|https://github.com/blerer/cassandra/commits/CASSANDRA-4762]. 
I have fixed all the points but I am not fully happy with the new name for the add method
of CompositesBuilder: {code}addElementToAll(ByteBuffer){code} and {code}addEachElementToAll(List<ByteBuffer>){code}.
I am willing to take any suggestion. I tried to make the javadoc explicite by providing some
examples to compensate for those not so clear names. 


was (Author: blerer):
Pushed the fix to [branch|https://github.com/blerer/cassandra/commits/CASSANDRA-4762]. 
I have fixed all the points but I am not fully happy with the new name for the add method
of CompositesBuilder: {quote}addElementToAll(ByteBuffer){quote} and {quote}addEachElementToAll(List<ByteBuffer>){quote}.
I am willing to take any suggestion. I tried to make the javadoc explicite by providing some
examples to compensate for those not so clear names. 

> 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)

Mime
View raw message