[
https://issues.apache.org/jira/browse/CASSANDRA-8603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552682#comment-14552682
]
Aleksey Yeschenko commented on CASSANDRA-8603:
----------------------------------------------
Committed to 2.1 as {{2248780eae46d98be8a9414d3e833fb6c16c7137}} and merged up,
thanks.
> Cut tombstone memory footprint in half for cql deletes
> ------------------------------------------------------
>
> Key: CASSANDRA-8603
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8603
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Dominic Letz
> Assignee: Benjamin Lerer
> Labels: tombstone
> Attachments: 8603-2.1-V3.txt, cassandra-2.0.11-8603.txt,
> cassandra-2.1-8603.txt, cassandra-2.1-8603_v2.txt, system.log
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
