cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2641) AbstractBounds.normalize should deal with overlapping ranges
Date Tue, 14 Jun 2011 19:54:47 GMT


Stu Hood commented on CASSANDRA-2641:

bq. getRestrictedRanges splits a range at different tokens.
You're right... that was my imagination.

+1 looks good!

> AbstractBounds.normalize should deal with overlapping ranges
> ------------------------------------------------------------
>                 Key: CASSANDRA-2641
>                 URL:
>             Project: Cassandra
>          Issue Type: Test
>          Components: Core
>            Reporter: Stu Hood
>            Assignee: Stu Hood
>            Priority: Minor
>             Fix For: 0.8.1
>         Attachments: 0001-Assert-non-overlapping-ranges-in-normalize.txt, 0001-Make-normalize-deoverlap-ranges.patch,
> Apparently no consumers have encountered it in production, but AbstractBounds.normalize
does not handle overlapping ranges. If given overlapping ranges, the output will be sorted
but still overlapping, for which SSTableReader.getPositionsForRanges will choose ranges in
an SSTable that may overlap.
> We should either add an assert in normalize(), or in getPositionsForRanges() to ensure
that this never bites us in production.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message