You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Christian Spriegel (JIRA)" <ji...@apache.org> on 2012/11/05 14:34:13 UTC
[jira] [Comment Edited] (CASSANDRA-4905) Repair should exclude
gcable tombstones from merkle-tree computation
[ https://issues.apache.org/jira/browse/CASSANDRA-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490106#comment-13490106 ]
Christian Spriegel edited comment on CASSANDRA-4905 at 11/5/12 1:34 PM:
------------------------------------------------------------------------
-Also I wonder if a expired column could create the digest of a tombstone if it is timed out.-
-If a gcable tombstone does not alter the digest, then a timed-out ExpiredColumn should behave like a tombstone.-
Edit: It already works like this
was (Author: christianmovi):
Also I wonder if a expired column could create the digest of a tombstone if it is timed out.
If a gcable tombstone does not alter the digest, then a timed-out ExpiredColumn should behave like a tombstone.
> Repair should exclude gcable tombstones from merkle-tree computation
> --------------------------------------------------------------------
>
> Key: CASSANDRA-4905
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4905
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Christian Spriegel
>
> Currently gcable tombstones get repaired if some replicas compacted already, but some are not compacted.
> This could be avoided by ignoring all gcable tombstones during merkle tree calculation.
> This was discussed with Sylvain on the mailing list:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/repair-compaction-and-tombstone-rows-td7583481.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira