[
https://issues.apache.org/jira/browse/CASSANDRA-8946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357027#comment-14357027
]
Benedict commented on CASSANDRA-8946:
-------------------------------------
I started fleshing out the unit tests for CASSANDRA-8939 to make them
exhaustive, and naturally this requires it actually honouring its bounds. I'm
not attacking it in a pretty way (that would involve refactoring the
AbstractBounds hierarchy, which would be messy merge-wise, and probably best
held off until later), but nor messily. I should upload a patch later today.
> 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)
