[
https://issues.apache.org/jira/browse/CASSANDRA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Dusbabek updated CASSANDRA-293:
------------------------------------
Attachment: 336-thrift.patch
I don't understand why I would want (as proposed in 336):
struct Deletion {
1: required i64 timestamp,
2: optional binary super_column,
3: optional binary SlicePredicate,
}
instead of:
struct Deletion {
1: required i64 timestamp,
2: required ColumnParent column_parent
3: required binary SlicePredicate,
}
The patch also proposes a remove_range_slice method.
> 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.
