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 2013/05/21 21:45:18 UTC
[jira] [Commented] (CASSANDRA-5398) Remove localTimestamp from
merkle-tree calculation (for tombstones)
[ https://issues.apache.org/jira/browse/CASSANDRA-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663303#comment-13663303 ]
Christian Spriegel commented on CASSANDRA-5398:
-----------------------------------------------
[~jbellis]: Would this ticket be a candidate for 1.2? It seems repair is getting a lot of attention lately, so there might be interest in reducing overrepair whereever possible.
> Remove localTimestamp from merkle-tree calculation (for tombstones)
> -------------------------------------------------------------------
>
> Key: CASSANDRA-5398
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5398
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Christian Spriegel
> Priority: Trivial
> Attachments: V1.patch
>
>
> DeletedColumn and RangeTombstone use the local-timestamp to update the digest during repair.
> Even though its only a second-precision timestamp, I think it still causes some differences in the merkle tree, therefore causing overrepair.
> I attached a patch on trunk that adds a modified updateDigest() to DeletedColumn, which does not use the value field for its calculation.
--
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