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/03/28 18:45:15 UTC

[jira] [Created] (CASSANDRA-5398) Remove localTimestamp from merkle-tree calculation (for tombstones)

Christian Spriegel created CASSANDRA-5398:
---------------------------------------------

             Summary: 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