[CASSANDRA-9759] RowAndTombstoneMergeIterator combine RangeTombstones even if they should not be

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0 alpha 1
• Component/s: Legacy/Local Write-Read Paths
• Severity: Normal
• Assignee: Benjamin Lerer
• Reporter: Benjamin Lerer

Authors

Benjamin Lerer

Reviewers

Sylvain Lebresne

• Created: 08/Jul/15 13:59
• Updated: 16/Apr/19 09:31
• Resolved: 13/Jul/15 13:48

Description

I noticed that the range tombstones [ ,0] and (2, ] got combine by the RowAndTombstoneMergeIterator even if they should not have been.

The result was the following:

Marker INCL_START_BOUND()@1436287022237000
Row: clustering=0 | value=0
Marker INCL_END_EXCL_START_BOUNDARY(0)@1436287022237000-1436287022196000
Row: clustering=1 | value=1
Row: clustering=2 | value=2
Row: clustering=3 | value=3
Row: clustering=4 | value=4
Marker INCL_END_BOUND()@1436287022196000

Issue Links

• is depended upon by: CASSANDRA-6237 Allow range deletions in CQL