[
https://issues.apache.org/jira/browse/CASSANDRA-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695523#comment-13695523
]
Jonathan Ellis commented on CASSANDRA-5712:
-------------------------------------------
Do we really need rangeTombstonesReversed? ISTM that we could just special
case tombstones in addColumn (rename to addAtom) to always addFirst regardless
of reversed-ness.
> Reverse slice queries can skip range tombstones
> -----------------------------------------------
>
> Key: CASSANDRA-5712
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5712
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 1.2.7
>
> Attachments: 5712.txt
>
>
> On disk, we represent range tombstones by a marker at the beginning of the
> range covered. Since we repeat such markers when they overlap an index block
> and since an index block is always read in forward order (even in reverse
> queries), we are guaranteed to see a range tombstone before any column it
> covers. However, IndexedSliceReader returns the columns of an index block in
> reverse order and thus can return a range tombstone *after* columns it covers.
> It follows that some range tombstone can be skipped during a reversed range
> slice. We need to fix IndexedSliceReader to always return range tombstone
> first (or at least before the first column covered by each range tombstone).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
