[jira] Resolved: (CASSANDRA-293) remove_key_range operation

["Gary Dusbabek (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Dusbabek resolved CASSANDRA-293.
-------------------------------------

    Resolution: Won't Fix

Range operations cannot be made to work with the existing implementation of hinted handoff.  Further, they were a bad fit for the transactional units in cassandra (column family ops).

CASSANDRA-494 will implement remove_slice for a single key and will also allow Deletion to be specified in a batch_mutation.

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