[CASSANDRA-8603] Cut tombstone memory footprint in half for cql deletes

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.1.6, 2.2.0 rc1
• Component/s: Legacy/Local Write-Read Paths
• Labels: tombstone
• Assignee: Benjamin Lerer
• Reporter: Dominic Letz

Authors

Benjamin Lerer

Reviewers

Aleksey Yeschenko

• Created: 13/Jan/15 08:51
• Updated: 16/Apr/19 09:31
• Resolved: 20/May/15 17:08

Description

As CQL does not yet support range deletes every delete from CQL results in a "Semi-RangeTombstone" which actually has the same start and end values - but until today they are copies. Effectively doubling the required heap memory to store the RangeTombstone.

Issue Links

• is related to: CASSANDRA-6237 Allow range deletions in CQL