[jira] [Commented] (CASSANDRA-13340) Bugs handling range tombstones in the sstable iterators

["Michael Kjellman (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929099#comment-15929099 ] 

Michael Kjellman commented on CASSANDRA-13340:
----------------------------------------------

did you mean to commit this line in one of the unit tests commented out?

https://github.com/pcmanus/cassandra/commit/66100ffecba6ff55027f6e85b29efaf98700edaa#diff-70d3a7f61389330811d6eb2f7d2d1b76R1391

> Bugs handling range tombstones in the sstable iterators
> -------------------------------------------------------
>
>                 Key: CASSANDRA-13340
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13340
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Critical
>             Fix For: 3.0.x, 3.11.x
>
>
> There is 2 bugs in the way sstable iterators handle range tombstones:
> # empty range tombstones can be returned due to a strict comparison that shouldn't be.
> # the sstable reversed iterator can actually return completely bogus results when range tombstones are spanning multiple index blocks.
> The 2 bugs are admittedly separate but as they both impact the same area of code and are both range tombstones related, I suggest just fixing both here (unless something really really mind).
> Marking the ticket critical mostly for the 2nd bug: it can truly make use return bad results on reverse queries.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)