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 2014/09/19 22:25:34 UTC

[jira] [Commented] (CASSANDRA-7538) Truncate of a CF should also delete Paxos CF

    [ https://issues.apache.org/jira/browse/CASSANDRA-7538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141233#comment-14141233 ] 

Aleksey Yeschenko commented on CASSANDRA-7538:
----------------------------------------------

We don't truncate hints or batchlog, but both look at the truncation records when deciding whether or not to replay a particular mutation.

> Truncate of a CF should also delete Paxos CF
> --------------------------------------------
>
>                 Key: CASSANDRA-7538
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7538
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: sankalp kohli
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>
> We don't delete data from Paxos CF during truncate. This will cause data to come back in the next CAS round for incomplete commits. 
> Also I am not sure whether we already do this but should we also not truncate hints for that CF. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)