You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2012/09/14 23:46:07 UTC
[jira] [Updated] (CASSANDRA-4667) optimize memtable deletions for
batchlog
[ https://issues.apache.org/jira/browse/CASSANDRA-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko updated CASSANDRA-4667:
-----------------------------------------
Attachment: CASSANDRA-4667-v1.patch
> optimize memtable deletions for batchlog
> ----------------------------------------
>
> Key: CASSANDRA-4667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4667
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Attachments: CASSANDRA-4667-v1.patch
>
>
> Batchlog writes with the same key are never retried. This means that if a batchlog row is in the memtable, it can't be in any of the sstables, ever. In such cases we don't need to write a tombstone to disk. We can purge the row completely from the memtable and only write a tombstone if the row had been flushed already (if it's not in the memtable then it must be in one of the sstables).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira