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 2009/11/06 18:04:32 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:
-------------------------------------

    Description: 
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.

  was:
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.


> 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
>            Priority: Minor
>
> 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.