You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Coli (JIRA)" <ji...@apache.org> on 2013/09/20 20:27:53 UTC

[jira] [Commented] (CASSANDRA-5502) Secondary Index Storage

    [ https://issues.apache.org/jira/browse/CASSANDRA-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773276#comment-13773276 ] 

Robert Coli commented on CASSANDRA-5502:
----------------------------------------

You can do this without a Cassandra code change by simply implementing your own secondary index columnfamily.

That said, given secondary indexes are columnfamilies and columnfamilies are in their own directories in part so that you can store them on different mountpoints, this ticket seems reasonable to me.

+1
                
> Secondary Index Storage
> -----------------------
>
>                 Key: CASSANDRA-5502
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5502
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Brooke Bryan
>
> Currently, both the CF data, and the secondary index data are stored within the same folder on disk.  Being able to split these into separate folders could be a great improvement with performance.  With our data, and secondary index, we will query the index a lot more, so can optimise hardware for the two traffic shapes coming through.
> Something like /Keyspace/CF/indexes/indexname/*.db
> Not too sure how much would be involved to change this, but I would imagine fairly cheap cost to reward.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira