You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/01/18 19:52:54 UTC
[jira] Updated: (CASSANDRA-531) truncate support
[ https://issues.apache.org/jira/browse/CASSANDRA-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-531:
-------------------------------------
Affects Version/s: 0.7
> truncate support
> ----------------
>
> Key: CASSANDRA-531
> URL: https://issues.apache.org/jira/browse/CASSANDRA-531
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Chris Goffinet
> Priority: Minor
> Fix For: 0.6
>
> 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.