[
https://issues.apache.org/jira/browse/CASSANDRA-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032652#comment-13032652
]
Stu Hood edited comment on CASSANDRA-2641 at 5/12/11 8:33 PM:
--------------------------------------------------------------
bq. merge intersecting ranges (it makes sense a "normalize" function would do
that and it's fairly trivial)
Famous last words =)
EDIT: But yes, I agree that this is the nicest approach.
was (Author: stuhood):
bq. merge intersecting ranges (it makes sense a "normalize" function would
do that and it's fairly trivial)
Famous last words =)
> AbstractBounds.normalize should deal with overlapping ranges
> ------------------------------------------------------------
>
> Key: CASSANDRA-2641
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2641
> Project: Cassandra
> Issue Type: Test
> Components: Core
> Reporter: Stu Hood
> Assignee: Stu Hood
> Priority: Minor
> Fix For: 1.0
>
>
> 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: http://www.atlassian.com/software/jira
