cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-531) truncate support
Date Mon, 03 May 2010 15:15:02 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863372#action_12863372
] 

Jonathan Ellis commented on CASSANDRA-531:
------------------------------------------

getting 8 or 9 patch failures, can you rebase to latest trunk?

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


Mime
View raw message