[
https://issues.apache.org/jira/browse/CASSANDRA-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858175#action_12858175
]
Stu Hood commented on CASSANDRA-749:
------------------------------------
I think we agree that both approaches have their merits. The vast difference
between their best use cases needs to be considered as we decide on a query
API. In particular:
Local indexes are better for:
* Low cardinality fields
* Filtering of values in base order
Distributed indexes are better for:
* High cardinality fields
* Querying of values in index order
Since we've decided to move forward with local indexes in this version, I think
it would be reasonable to restrict this initial implementation to filtering of
known keys (no sorting), and to put a restriction (like the null rows) in place
to prevent them from being used for querying. Additionally, we should "leave
room" to add in the ability to sort/query on the indexed dimension in the
future (when we implement distributed indexes).
> Secondary indices for column families
> -------------------------------------
>
> Key: CASSANDRA-749
> URL: https://issues.apache.org/jira/browse/CASSANDRA-749
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Priority: Minor
> Fix For: 0.8
>
> Attachments: 0001-simple-secondary-indices.patch,
> views-discussion-2.txt, views-discussion.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
