[
https://issues.apache.org/jira/browse/CASSANDRA-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829247#action_12829247
]
Stu Hood commented on CASSANDRA-749:
------------------------------------
> you mean, make each machine hold a copy of the full index?
I mean a distributed secondary index would be stored in a true ColumnFamily, so
it would be partitioned like any other CF.
> let's keep this ticket's scope to just automating using another CF to look up
> keys by value.
In the local secondary index case, perhaps rather than using a separate column
family, the index should be another component of the ColumnFamilyStore, tied to
each Memtable/SSTable, rather than being a separate ColumnFamily. This gains us
a lot of efficiency, and some consistency.
We already have the primary index file (Index.db) on disk, so secondary indexes
would be similar: (column, datafile_offset) tuples. Consistency wise, all
replication and repairs happen at the ColumnFamily level, so replication might
repair the data ColumnFamily but not its index for instance.
> 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.
