[
https://issues.apache.org/jira/browse/CASSANDRA-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849822#action_12849822
]
Jonathan Ellis commented on CASSANDRA-531:
------------------------------------------
CASSANDRA-699 is probably a better approach for "I want to delete data older
than X," so IMO truncate should focus on the "wipe everything clean," i.e.,
let's drop the "truncateBefore" stuff at least initially.
It would be nice to add a Truncation "super-tombstone" to the commitlog so that
we can replay and repair the Truncate in the face of node failure but I think
the biggest use case here is for testing and/or playing, so I'm fine with
punting on that until someone actually needs it.
> truncate support
> ----------------
>
> Key: CASSANDRA-531
> URL: https://issues.apache.org/jira/browse/CASSANDRA-531
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Chris Goffinet
> Priority: Minor
> Fix For: 0.7
>
> Attachments: 0001-CASSANDRA-531-add-truncate-truncateBefore.txt,
> 0002-add-unimplemented-truncate-to-thrift-API.txt
>
>
> Sometimes you want to delete an entire columnfamily. If there is a lot of
> data, it's much faster to just insert something to the commitlog saying
> "truncated," and drop the memtable and data files.
> Probably should require this to block for all replicas to ack to avoid
> unpleasant surprises. Or make it local-only and have ops manage making sure
> it gets to all replicas.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
