[
https://issues.apache.org/jira/browse/CASSANDRA-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-531:
-------------------------------------
Attachment: CASSANDRA-531.patch
Attached is a version with a few changes. The major one from a functionality
perspective is, we rely on the markCompacted to delete the files eventually.
Manually deleting them ahead of that can cause errors on concurrent reads.
Two things still need work. One is, we don't want to delete data that we
didn't snapshot; that could be a nasty surprise. I sketched out what I think
that could look like; SSTableReader.newSince is left as a TODO.
The other is minor -- truncate from cmdline should go in clustertool, not
nodetool. (Nodetool is for per-node ops.)
> 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.
