cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ran Tavory (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-531) truncate support
Date Sat, 01 May 2010 20:45:58 GMT


Ran Tavory updated CASSANDRA-531:

    Attachment: CASSANDRA-531.patch

In this patch I think I completed all the thrift wiring work, including internal messaging
to all hosts in the cluster.
The patch includes all previous changes, no need to use the previous patches.
I've also removed the timestamp from the truncation signature since it's not used.

Delete the actual files???... not sure what I should do... What's the effect of marking all
sstables as compacted? 
Add truncate to the JMX interface
Add truncate to nodetool
Add system tests to test nodetool + JMX

> truncate support
> ----------------
>                 Key: CASSANDRA-531
>                 URL:
>             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
> 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