开发者

When I remove rows in Cassandra I delete only columns not row keys

开发者 https://www.devze.com 2023-01-02 22:39 出处:网络
If I delete every keys in a ColumnFamily in a Cassandra db usin开发者_Python百科g remove(key), then if I use get_range_slices, rows are still there but without columns. How could I remove entire rows?

If I delete every keys in a ColumnFamily in a Cassandra db usin开发者_Python百科g remove(key), then if I use get_range_slices, rows are still there but without columns. How could I remove entire rows?


Why do deleted keys show up during range scans?

Because get_range_slice says, "apply this predicate to the range of rows given," meaning, if the predicate result is empty, we have to include an empty result for that row key. It is perfectly valid to perform such a query returning empty column lists for some or all keys, even if no deletions have been performed.


Cassandra uses Distributed Deletes as expected.

Thus, a delete operation can't just wipe out all traces of the data being removed immediately: if we did, and a replica did not receive the delete operation, when it becomes available again it will treat the replicas that did receive the delete as having missed a write update, and repair them! So, instead of wiping out data on delete, Cassandra replaces it with a special value called a tombstone. The tombstone can then be propagated to replicas that missed the initial remove request.

http://wiki.apache.org/cassandra/DistributedDeletes


Just been having the same issue and I found that:

This has been fixed in 0.7 (https://issues.apache.org/jira/browse/CASSANDRA-1027). And backported to 0.6.3

This is also relevant: https://issues.apache.org/jira/browse/CASSANDRA-494

0

精彩评论

暂无评论...
验证码 换一张
取 消