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

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/11/12 22:15:12 UTC

[jira] [Resolved] (CASSANDRA-4906) Avoid flushing other columnfamilies on truncate

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

Jonathan Ellis resolved CASSANDRA-4906.
---------------------------------------

    Resolution: Fixed

Yes, backporting is probably straightforward.  But we shouldn't risk 1.1 stability with a new approach at this point.
                
> Avoid flushing other columnfamilies on truncate
> -----------------------------------------------
>
>                 Key: CASSANDRA-4906
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4906
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 1.2.0
>
>         Attachments: 4906.txt, 4906-v2.txt
>
>
> Currently truncate flushes *all* columnfamilies so it can get rid of the commitlog segments containing truncated data.  Otherwise, it could be replayed on restart since the replay position is contained in the sstables we're trying to delete.

--
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