[
https://issues.apache.org/jira/browse/CASSANDRA-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829403#action_12829403
]
Stu Hood commented on CASSANDRA-749:
------------------------------------
I've been thinking about this more, and I don't think implementing secondary
indexes is worth it: distributed or otherwise. Instead, I think the 'view'
approach that CouchDB and Riak have taken is definitely superior.
For instance, it is easy to implement a secondary index as a view of a
ColumnFamily: the key for the view is the value of the indexed column, and the
value for the view is the key of the original row. But views are considerably
more powerful, since you can store any item in the key or value for the view.
Also, a view is more conducive to duplication of data, which we prefer in
Cassandra: rather than having secondary indexes pointing to the one true copy
of the data, you can duplicate that data in a view if you'd like, and have it
be lazily/eagerly updated serverside.
Yes, views might mean a server side scripting language, or an easy to way to
plug in and configure Java view classes. It might even mean map-reduce.
> 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.6
>
> Attachments: 0001-simple-secondary-indices.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
