[
https://issues.apache.org/jira/browse/CASSANDRA-7969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-7969:
---------------------------------------
Attachment: 0001-track-min-max-timestamps-and-maxLocalDeletionTime-v2.patch
attaching v2, which truncates the cfs before running the 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)
