[
https://issues.apache.org/jira/browse/CASSANDRA-7969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149225#comment-14149225
]
Marcus Eriksson commented on CASSANDRA-7969:
--------------------------------------------
pushed a commit on top of this here:
https://github.com/krummas/cassandra/commit/cdaeefe54277975e3f25b3a6e2f5bf08bbde876d
creates a Max/MinTracker that keeps the logic and makes sure we always have a
default that makes sense if no cells/etc were found (which shouldn't happen..).
also adds a bunch of CQL tests
> Properly track min/max timestamps and maxLocalDeletionTimes for range and row
> tombstones
> ----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-7969
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7969
> Project: Cassandra
> Issue Type: Bug
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 2.0.11
>
> Attachments:
> 0001-track-min-max-timestamps-and-maxLocalDeletionTime-co.patch,
> 0001-track-min-max-timestamps-and-maxLocalDeletionTime-v2.patch
>
>
> First problem is that when we have only row or range tombstones in an sstable
> we dont update the maxLocalDeletionTime for the sstable
> Second problem is that if we have a range tombstone in an sstable,
> minTimestamp will always be Long.MIN_VALUE for flushed sstables due to how we
> set the default values for the variables
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
