I'm not sure about that — allowing collections as a primary key would be a
much different implementation than setting up a secondary index.
The primary key in CQL3 is actually the partition key which determines
which token the row is assigned, so you would still need to have one
partition key. Als
Ah, that is interesting, Patricia. Since they can be a secondary index,
it's not too far off for them being able to be a primary key, no?
On Mon, May 19, 2014 at 1:54 PM, Patricia Gorla
wrote:
> Raj,
>
> Secondary indexes across CQL3 collections were introduced into 2.1 beta1,
> so will be avail
Thanks Eric for the information. It looks like it will be supported in
future versions.
Raj
On Mon, May 19, 2014 at 10:03 AM, Eric Plowe 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.
Thank you Patricia. This is helpful.
Raj
On Mon, May 19, 2014 at 10:54 AM, Patricia Gorla wrote:
> 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 yo
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
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
wrote:
> Hello all,
>
> I am using Cassandra version 2.0.7
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
