You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benjamin Lerer (JIRA)" <ji...@apache.org> on 2015/12/07 15:52:11 UTC

[jira] [Updated] (CASSANDRA-8603) Cut tombstone memory footprint in half for cql deletes

     [ https://issues.apache.org/jira/browse/CASSANDRA-8603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Lerer updated CASSANDRA-8603:
--------------------------------------
    Component/s: Local Write-Read Paths

> 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: Local Write-Read Paths
>            Reporter: Dominic Letz
>            Assignee: Benjamin Lerer
>              Labels: tombstone
>             Fix For: 2.1.6, 2.2.0 rc1
>
>         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)