You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Mark Robson (JIRA)" <ji...@apache.org> on 2009/07/14 16:52:15 UTC
[jira] Created: (CASSANDRA-293) remove_key_range operation
remove_key_range operation
--------------------------
Key: CASSANDRA-293
URL: https://issues.apache.org/jira/browse/CASSANDRA-293
Project: Cassandra
Issue Type: New Feature
Reporter: Mark Robson
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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "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 updated CASSANDRA-293:
------------------------------------
Attachment: (was: 293-thrift-with-cf.diff)
> 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
>
>
> 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.
[jira] Commented: (CASSANDRA-293) remove_key_range operation
Posted by "Mark Robson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780294#action_12780294 ]
Mark Robson commented on CASSANDRA-293:
---------------------------------------
Hi All,
I have been quite amazed at the rate of development of Cassandra - only a
few months ago I was playing with the (relatively) limited 0.3 version, now
a lot of the bugs - even the really tricky ones have been fixed and loads of
good stuff is being done all the time.
This is definitely an example of open source software moving forward at an
incredible rate. Just now I still can't use Cassandra in production, but by
the time I'm ready for it, it may be ready for me, at this rate!
Keep the good work up chaps,
Mark
(NB: this is a feature request I added some time ago)
2009/11/19 Jonathan Ellis (JIRA) <ji...@apache.org>
> 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
>
>
> 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.
[jira] Commented: (CASSANDRA-293) remove_key_range operation
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780648#action_12780648 ]
Jonathan Ellis commented on CASSANDRA-293:
------------------------------------------
CASSANDRA-336 proposes a Deletion thrift struct, combining a SlicePredicate and a timestamp. Using that is probably the way to go, for consistency.
> 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
>
>
> 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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-293:
-------------------------------------
Fix Version/s: 0.9
> 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
> Priority: Minor
> Fix For: 0.9
>
>
> 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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-293:
-------------------------------------
Fix Version/s: (was: 0.6)
0.7
> 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: 293-thrift-with-cf.diff, 293-v1.diff
>
>
> 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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "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 updated CASSANDRA-293:
------------------------------------
Attachment: 293-thrift.diff
Proposed thrift changes.
> 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: 293-thrift.diff
>
>
> 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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-293:
-------------------------------------
Priority: Minor (was: Major)
> remove_key_range operation
> --------------------------
>
> Key: CASSANDRA-293
> URL: https://issues.apache.org/jira/browse/CASSANDRA-293
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Mark Robson
> Priority: Minor
>
> 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.
[jira] Commented: (CASSANDRA-293) remove_key_range operation
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "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 updated CASSANDRA-293:
------------------------------------
Attachment: 0006-alter-hint-format.patch
0005-unit-tests.patch
0004-RangeRemoveCommand-and-LocalRangeDeletion.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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "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 updated CASSANDRA-293:
------------------------------------
Attachment: 293-v1.diff
This patch implements the feature except 1) handling hinted handoff and 2) consistency_level checking in the initial call into StorageProxy.
> 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: 293-thrift-with-cf.diff, 293-v1.diff
>
>
> 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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "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 updated CASSANDRA-293:
------------------------------------
Attachment: (was: 293-v1.diff)
> 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
>
>
> 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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "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 updated CASSANDRA-293:
------------------------------------
Attachment: (was: 293-thrift.diff)
> 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: 293-thrift-with-cf.diff
>
>
> 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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "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 updated CASSANDRA-293:
------------------------------------
Attachment: 0003-remove-unused-parts-of-WriteResponse.patch
0002-add-flexibility-to-commit-log-serialization.patch
0001-thrift-changes.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.
[jira] Commented: (CASSANDRA-293) remove_key_range operation
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786923#action_12786923 ]
Jonathan Ellis commented on CASSANDRA-293:
------------------------------------------
am I missing something, or is there no CF param?
> 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: 293-thrift.diff
>
>
> 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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "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 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.
[jira] Assigned: (CASSANDRA-293) remove_key_range operation
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-293:
----------------------------------------
Assignee: Gary Dusbabek
like get_range_slice, we want remove_range_slice taking similar parameters w/ a timestamp for the delete op
> 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
>
>
> 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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "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 updated CASSANDRA-293:
------------------------------------
Attachment: 293-thrift-with-cf.diff
includes a cf param now.
> 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: 293-thrift-with-cf.diff
>
>
> 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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "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 updated CASSANDRA-293:
------------------------------------
Attachment: 0007-refactor-HHOM-to-handle-new-hint-format.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.
[jira] Commented: (CASSANDRA-293) remove_key_range operation
Posted by "Gasol Wu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738261#action_12738261 ]
Gasol Wu commented on CASSANDRA-293:
------------------------------------
the RowMutation.delete() that have some condition like below, so i can't batch remove columns, does there have any concern about it?
if (modifications_.containsKey(cfName))
{
throw new IllegalArgumentException("ColumnFamily " + cfName + " is already being modified");
}
> 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
> Priority: Minor
>
> 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.
[jira] Updated: (CASSANDRA-293) remove_key_range operation
Posted by "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 updated CASSANDRA-293:
------------------------------------
Attachment: (was: 336-thrift.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.9
>
>
> 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.