[
https://issues.apache.org/jira/browse/CASSANDRA-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ran Tavory updated CASSANDRA-531:
---------------------------------
Attachment: CASSANDRA-531.patch
Make code up to date with recent trunk (0.7.0 trunk)
This patch includes: thrift and ColumnFamilyStore code (and test).
TODO:
1. wire up the thrift call from CassandraServer to here
2. Do I need to also delete actual files? Have I covered all scenarios?
3. Send the truncate operation to all nodes; make sure they are all up before
doing so
4. Add truncate to the JMX interface
5. Add truncate to nodetool
> 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
>
>
> 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.
