[
https://issues.apache.org/jira/browse/CASSANDRA-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431994#comment-13431994
]
Sylvain Lebresne commented on CASSANDRA-4511:
---------------------------------------------
I'll note that support for lists should be fairly simple following
CASSANDRA-3680. I haven't tried yet but it might well even be that it works out
of the box. It would be the same for indexing based on map values.
However, indexing based on set values (or on map keys, but I don't know if we
want that) is more complicated, because we need to index one of the component
of the composite name, so it probably require a new Searcher.
> 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
> Reporter: Sylvain Lebresne
> Priority: Minor
> Fix For: 1.2
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
