[
https://issues.apache.org/jira/browse/CASSANDRA-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066653#comment-13066653
]
Jonathan Ellis commented on CASSANDRA-2904:
-------------------------------------------
bq. would probably need some pointers for some things (how to handle a
compaction, query cursors and a consistency level other than ONE, mostly)
Probably the best place would be to add logic to RowIteratorFactory.getIterator
to recognize the empty predicate, and write a SSTableIndexScanner along the
lines of SSTableScanner to use in that situation.
You don't need to worry about compaction (the existing mechanisms to not purge
in-use sstables continue to work) or consistencylevel (handled at the
coordinator, not the replica owner).
> get_range_slices with no columns could be made faster by scanning the index
> file
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-2904
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2904
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jean-Francois Im
> Priority: Minor
>
> When scanning a column family using get_range_slices() and a predicate that
> contains no columns, the scan operates on the actual data, not the index file.
> Our use case for this is that we have a column family that has relatively
> wide rows(varying from 10kb to over 100kb of data per row) and we need to do
> iterate through all the keys to figure out which rows we are interested in;
> obviously, going through the index file than the data is faster in this
> case(in the order of minutes versus hours).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
