Currently cassandra supports "read repair," i.e., lazy repair when a read is done. This is better than nothing but is not sufficient for some cases (e.g. catastrophic node failure where you need to rebuild all of a node's data on a new machine).
Dynamo uses merkle trees here. This is harder for Cassandra given the CF data model but I suppose we could just hash the serialized CF value.
|Field||Original Value||New Value|
|Fix Version/s||0.5 [ 12314040 ]|
|Fix Version/s||0.4 [ 12313862 ]|
|Assignee||Stu Hood [ stuhood ]|
|Comment||[ Shoot. Just noticed a fundamental problem with using a Treap: going to need to think about the problem a bit more. ]|
|Component/s||Core [ 12312978 ]|
|Attachment||CASSANDRA-193.diff [ 12415086 ]|
|Status||Patch Available [ 10002 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Workflow||no-reopen-closed, patch-avail [ 12464046 ]||patch-available, re-open possible [ 12751900 ]|
|Workflow||patch-available, re-open possible [ 12751900 ]||reopen-resolved, no closed status, patch-avail, testing [ 12757996 ]|