[
https://issues.apache.org/jira/browse/CASSANDRA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865762#action_12865762
]
Gary Dusbabek commented on CASSANDRA-293:
-----------------------------------------
jbellis> gdusbabek: for #293, i'm thinking that we don't want to allow deleting
ranges of rows. we have too much stuff that's row-oriented, to have a
tombstone representing a range of rows, to fit in sanely
jbellis> allowing deleting column ranges is ugly, but more doable
gdusbabek> fuuuuuuuuuuuuu
gdusbabek> that simplifies the problem greatly though.
jbellis> sorry, i started thinking how we could implement HH when you were
complaining about how it was a bitch
jbellis> and the more i think the more it just seems like a bad fit
gdusbabek> it really is.
> 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.
