Sam Tunnicliffe commented on CASSANDRA-14513:

Trivial fix is to correctly adjust the current index pointer in IndexState when 
the slice bounds are found to be wholly before the start of the partition. It 
might make sense to open a follow up JIRA to investigate whether the 
modification of the tombstone bounds (in 
{{RangeTombstoneList::reverseIterator}}, and maybe {{forwardIterator}} if 
necessary) can be tightened up by asserting that any newly generated bounds are 
not disjoint from the query slice.



> Reverse order queries in presence of range tombstones may cause permanent 
> data loss
> -----------------------------------------------------------------------------------
>                 Key: CASSANDRA-14513
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14513
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core, CQL, Local Write-Read Paths
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Blocker
>             Fix For: 3.0.x, 3.11.x, 4.0.x
> Slice queries in descending sort order can create oversized artificial range 
> tombstones. At CL > ONE, read repair can propagate these tombstones to all 
> replicas, wiping out vast data ranges that they mistakenly cover.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to