[
https://issues.apache.org/jira/browse/CASSANDRA-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863981#action_12863981
]
Ran Tavory commented on CASSANDRA-531:
--------------------------------------
Moving the truncate operation from nodetool to cluster tool was easy enough.
I remove the unused ctx as well.
I don't know how to implement the SSTableReader.newSince (or SSTable.newSince).
need help here...
I'll upload the patch with my recent changes as mentioned above.
> 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
>
>
> 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.
