You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tupshin Harper (JIRA)" <ji...@apache.org> on 2011/09/07 22:47:09 UTC

[jira] [Issue Comment Edited] (CASSANDRA-2904) get_range_slices with no columns could be made faster by scanning the index file

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

Tupshin Harper edited comment on CASSANDRA-2904 at 9/7/11 8:46 PM:
-------------------------------------------------------------------

Added a patch that adds a SSTableIndexScanner and related changes per Jonathan's suggest

      was (Author: tupshin):
    Adds SSTableIndexScanner per Jonathan's suggest
  
> 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
>         Attachments: CASSANDRA-2904-v1.diff
>
>
> 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