Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <1981593626.49861270667793537.JavaMail.jira@brutus.apache.org>
Date: Wed, 7 Apr 2010 19:16:33 +0000 (UTC)
From: "Jeff Hodges (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-293) remove_key_range operation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jeff Hodges commented on CASSANDRA-293:
---------------------------------------

Gary, can you update this patch?

> remove_key_range operation
> --------------------------
>
>                 Key: CASSANDRA-293
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-293
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Mark Robson
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: 0001-thrift-changes.patch, 0002-add-flexibility-to-commit-log-serialization.patch, 0003-remove-unused-parts-of-WriteResponse.patch, 0004-RangeRemoveCommand-and-LocalRangeDeletion.patch, 0005-unit-tests.patch, 0006-alter-hint-format.patch, 0007-refactor-HHOM-to-handle-new-hint-format.patch
>
>
> For cleaning up old data on a rotating basis, a removal operation which operates on key ranges would be very handy, currently we have to remove every single column individually.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.