[
https://issues.apache.org/jira/browse/CASSANDRA-8946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357092#comment-14357092
]
Benedict commented on CASSANDRA-8946:
-------------------------------------
Patch available [here|https://github.com/belliottsmith/cassandra/tree/8946],
including relatively exhaustive unit tests - IMO we should follow up with a
refactor to flatten the entire AbstractBounds hierarchy, but that's a cleanup
for later
> 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)
