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

Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2015/01/13 14:40:34 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14275190#comment-14275190 ] 

Sylvain Lebresne commented on CASSANDRA-8603:
---------------------------------------------

Have you actually tested and validated that this was actually used? Because unless I'm missing something no range tombstone generated by CQL should have the same start and stop (it wouldn't entirely illegal to have a RT with the same start and stop, but this RT would select a single cell and bug excluded, we use cell tombstones for that case, not range tombstones).

> 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
>              Labels: tombstone
>         Attachments: cassandra-2.0.11-8603.txt, cassandra-2.1-8603.txt
>
>
> 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)