cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-5502) Secondary Index Storage
Date Fri, 18 Mar 2016 20:52:33 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aleksey Yeschenko resolved CASSANDRA-5502.
------------------------------------------
    Resolution: Won't Fix

As we are very likely moving to making SASI (CASSANDRA-10661) the new default implementation
(CASSANDRA-11075), and indexes are components of sstables there, closing the ticket as Won't
Fix.

> Secondary Index Storage
> -----------------------
>
>                 Key: CASSANDRA-5502
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5502
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Brooke Bryan
>            Priority: Minor
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message