cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8946) Make SSTableScanner always respect its bound
Date Wed, 11 Mar 2015 16:01:38 GMT


Benedict commented on CASSANDRA-8946:

Patch available [here|], 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:
>             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

View raw message