[
https://issues.apache.org/jira/browse/CASSANDRA-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827676#comment-13827676
]
Sylvain Lebresne commented on CASSANDRA-4511:
---------------------------------------------
bq. Does sound like we have a consensus for indexing map keys.
Yep, but as said above, I'd rather tackle the remaining bits of that in
CASSANDRA-6383 since there a few added difficulties related to the 2ndary index
API.
We do need to decide though, do we stick to CONTAINS here (and use CONTAINS KEY
in CASSANDRA-6383) or do we prefer IN (and we need a new idea for
CASSANDRA-6383). I personally have a slight preference for CONTAINS just
because the extension to map keys seems more straightforward, but I don't care
a whole lot otherwise.
> Secondary index support for CQL3 collections
> ---------------------------------------------
>
> Key: CASSANDRA-4511
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4511
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 1.2.0 beta 1
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 2.1
>
> Attachments: 4511.txt
>
>
> We should allow to 2ndary index on collections. A typical use case would be
> to add a 'tag set<String>' to say a user profile and to query users based on
> what tag they have.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
