[
https://issues.apache.org/jira/browse/CASSANDRA-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863877#action_12863877
]
Jonathan Ellis commented on CASSANDRA-531:
------------------------------------------
Oh, also the commitlog context stuff is redundant since snapshot flushes, and
flush already marks the commitlog "don't bother replaying stuff before this"
and cleans up obsolete segments. I removed the CommitLog method calls, but I
didn't r/m the ctx creation, so that can go too.
> 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: Ran Tavory
> Priority: Minor
> Fix For: 0.7
>
> Attachments: 0001-CASSANDRA-531-add-truncate-truncateBefore.txt,
> 0002-add-unimplemented-truncate-to-thrift-API.txt, CASSANDRA-531.patch,
> CASSANDRA-531.patch, CASSANDRA-531.patch, CASSANDRA-531.patch,
> CASSANDRA-531.patch, CASSANDRA-531.patch, CASSANDRA-531.patch,
> CASSANDRA-531.patch, CASSANDRA-531.patch, CASSANDRA-531.patch
>
>
> 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.
