You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2015/03/11 17:12:38 UTC

[jira] [Updated] (CASSANDRA-8946) Make SSTableScanner always respect its bound

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

Benedict updated CASSANDRA-8946:
--------------------------------
    Fix Version/s: 2.1.4

> Make SSTableScanner always respect its bound
> --------------------------------------------
>
>                 Key: CASSANDRA-8946
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8946
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Sylvain Lebresne
>            Assignee: Benedict
>             Fix For: 2.1.4
>
>
> When {{SSTableScanner}} takes a {{DataRange}}, it doesn't fully respect the bounds provided as it always generate a {{Bounds}} object, thus potentially ending up including a key it should have excluded. It's currently compensated by in {{ColumnFamilyStore.getSequentialIterator}} but that is still an unexpected behavior and is such error prone. We should fix that and remove the compensation in {{ColumnFamilyStore.getSequentialIterator}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)