[CASSANDRA-9596] Tombstone timestamps aren't used to skip SSTables while they are still in the memtable

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Fix Version/s: 2.1.x
• Assignee: Unassigned
• Reporter: Richard Low
• Created: 12/Jun/15 21:54
• Updated: 16/Apr/19 09:31
• Resolved: 15/Jan/16 16:53

Description

If you have one SSTable containing a partition level tombstone at timestamp t and all other SSTables have cells with timestamp < t, Cassandra will skip all the other SSTables and return nothing quickly. However, if the partition tombstone is still in the memtable it doesn’t skip any SSTables. It should use the same timestamp logic to skip all SSTables.

Issue Links

• duplicates: CASSANDRA-7394 Fix CollationController#collectTimeOrderedData() mostRecentRowTombstone tracking
• duplicates: CASSANDRA-9298 CollationController.collectAllData can be too conservative with sstable elimination