cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patricia Gorla <patri...@thelastpickle.com>
Subject Re: Filtering on Collections
Date Mon, 19 May 2014 17:54:58 GMT
Raj,

Secondary indexes across CQL3 collections were introduced into 2.1 beta1,
so will be available in future versions. See
https://issues.apache.org/jira/browse/CASSANDRA-4511

If your main concern is performance then you should find another way to
model the data: each collection is read entirely into memory to access a
single item.



On Mon, May 19, 2014 at 11:03 AM, Eric Plowe <eric.plowe@gmail.com> wrote:

> Collection types cannot be used for filtering (as part of the where
> statement).
> They cannot be used as a primary key or part of a primary key.
> Secondary indexes are not supported as well.
>
>
> On Mon, May 19, 2014 at 12:50 PM, Raj Janakarajan <raj@zephyrhealthinc.com
> > wrote:
>
>> Hello all,
>>
>> I am using Cassandra version 2.0.7.  I am wondering if "collections" is
>> efficient for filtering.  We are thinking of using "collections" to
>> maintain a list for a customer row but we have to be able to filter on the
>> collection values.
>>
>> Select UUID from customer where eligibility_state IN (CA, NC)
>>
>> Eligibility_state being a collection.  The above query would be used
>> frequently.
>> Would you recommend collections for modeling from a performance
>> perspective?
>>
>> Raj
>> --
>>
>>  Data Architect ❘ Zephyr Health
>>  589 Howard St. ❘ San Francisco, CA 94105
>> m: +1 9176477433 ❘ f: +1 415 520-9288
>>  o: +1 415 529-7649 | s: raj.janakarajan
>>
>> http://www.zephyrhealth.com
>>
>>
>


-- 
Patricia Gorla
@patriciagorla

Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com <http://thelastpickle.com>

Mime
View raw message