cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6389) Check first and last key to potentially skip SSTable for reads
Date Tue, 26 Nov 2013 22:15:36 GMT

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

Jonathan Ellis commented on CASSANDRA-6389:
-------------------------------------------

The "main" collationcontroller path would be fine with an assert but there's a dozen or so
other callers that would not be.  Going to leave it alone.

> Check first and last key to potentially skip SSTable for reads
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-6389
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6389
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Tyler Hobbs
>            Priority: Minor
>         Attachments: 6389.patch
>
>
> In {{SSTableReader.getPosition()}}, we use a -1 result from a binary search on the index
summary to check if the requested key falls before the start of the sstable.  Instead, we
can directly compare the requested key with the {{first}} and {{last}} keys for the sstable,
which will allow us to also skip keys that fall after the last key in the sstable.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message