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 16:24:39 UTC
[jira] [Assigned] (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 reassigned CASSANDRA-8946:
-----------------------------------
Assignee: Benedict
> Make SSTableScanner always respect its bound
> --------------------------------------------
>
> Key: CASSANDRA-8946
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8946
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Benedict
>
> 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)