cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-531) truncate support
Date Tue, 24 Nov 2009 15:55:39 GMT


Jonathan Ellis commented on CASSANDRA-531:

progress so far:

    add (unimplemented) truncate to thrift API

    CASSANDRA-531 add truncate, truncateBefore

If someone wants to wire up the thrift api to CFS.truncate, that would be awesome.

Let's use negative timestamp to indicate "truncate all".

The StorageProxy method should throw UnavailableException if any replica is down, or if there
is any node movement going on (any pending ranges in metadata).

> truncate support
> ----------------
>                 Key: CASSANDRA-531
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.9
>         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.

View raw message