[
https://issues.apache.org/jira/browse/CASSANDRA-9759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14620748#comment-14620748
]
Sylvain Lebresne commented on CASSANDRA-9759:
---------------------------------------------
Patch looks mostly good, but the call to {{RangeTombstone.Bound.Kind.compare}}
is now really redundant and should go away.
> RowAndTombstoneMergeIterator combine RangeTombstones even if they should not
> be
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-9759
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9759
> Project: Cassandra
> Issue Type: Bug
> Reporter: Benjamin Lerer
> Assignee: Benjamin Lerer
>
> 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:
> {code}
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
