cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7538) Truncate of a CF should also delete Paxos CF
Date Fri, 04 Dec 2015 20:40:11 GMT

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

Sam Tunnicliffe updated CASSANDRA-7538:
---------------------------------------
    Component/s: Coordination

> 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
>          Components: Coordination
>            Reporter: sankalp kohli
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>             Fix For: 2.0.12, 2.1.3
>
>         Attachments: 7538.txt
>
>
> 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)

Mime
View raw message