[CASSANDRA-7969] Properly track min/max timestamps and maxLocalDeletionTimes for range and row tombstones

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.0.11
• Severity: Normal
• Assignee: Marcus Eriksson
• Reporter: Marcus Eriksson

Authors

Marcus Eriksson

Reviewers

T Jake Luciani

• Created: 18/Sep/14 07:42
• Updated: 16/Apr/19 09:31
• Resolved: 02/Oct/14 08:51

Description

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