[
https://issues.apache.org/jira/browse/CASSANDRA-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825993#comment-13825993
]
Alex Cruise commented on CASSANDRA-4511:
----------------------------------------
FWIW I had a strong use case for indexing both map keys and values. The
indexing difficulties (not just in collections) are a big part of the reason I
ended up going back to postgres, at least temporarily. :)
My data is tagged with customer-supplied arbitrary name/values, and I need to
be able to search on both quickly.
> 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)
