You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/05/21 23:44:20 UTC
[jira] [Updated] (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:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-5398:
--------------------------------------
Reviewer: yukim
Priority: Minor (was: Trivial)
Fix Version/s: 1.2.6
Assignee: Christian Spriegel
> 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
> Assignee: Christian Spriegel
> Priority: Minor
> Fix For: 1.2.6
>
> 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