[
https://issues.apache.org/jira/browse/CASSANDRA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786208#action_12786208
]
Jonathan Ellis commented on CASSANDRA-293:
------------------------------------------
using optional SC there falls out of Mutation needing ColumnOrSuperColumn, so
all that needs is a CF to be a complete path. So since you have a CF in the
method params, all Deletion needs is the SC to be complete.
The alternative would be to create a new struct that was either a Column or a
list<Column> (both optional) and then you could have ColumnParent shared
between Deletion and this new ColumnOrListColumns struct. IMO one of our rules
of thumb should be to minimize one-off structs, so I perfer Deletion as given.
> 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.9
>
> Attachments: 336-thrift.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.
