[
https://issues.apache.org/jira/browse/CASSANDRA-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719386#action_12719386
]
Jonathan Ellis commented on CASSANDRA-193:
------------------------------------------
IRC: i am considering storing the hashes for an SSTable in another SSTable, to
prevent them from being recalculated
If it were useful to have the per-sstable hashes precalculated, we could keep
them in the SSTable itself (with the appropriate format change). The problem
is, that we need to hash the entire row, which means merging columns from
multiple sstables, which means no per-sstable hash will be useful.
Unless I am missing something, in which case, hurrah! :)
> Proactive repair
> ----------------
>
> Key: CASSANDRA-193
> URL: https://issues.apache.org/jira/browse/CASSANDRA-193
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jonathan Ellis
> Fix For: 0.4
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
