You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Johan Oskarsson (JIRA)" <ji...@apache.org> on 2010/08/10 21:26:16 UTC
[jira] Updated: (CASSANDRA-1375) Enable different sstable recovery
processeses
[ https://issues.apache.org/jira/browse/CASSANDRA-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johan Oskarsson updated CASSANDRA-1375:
---------------------------------------
Attachment: CASSANDRA-1375.patch
As per issue description. The TODO in the patch is where CASSANDRA-1072 hooks in, see that patch for context.
This patch also contains a refactoring of the AES code to prepare for unit tests of column families with other clock types.
> Enable different sstable recovery processeses
> ---------------------------------------------
>
> Key: CASSANDRA-1375
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1375
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Johan Oskarsson
> Attachments: CASSANDRA-1375.patch
>
>
> In CASSANDRA-1072 we need to perform a different sstable recovery process depending on streaming operation (AES, bootstrap etc). This issue seeks to split that refactoring out of CASSANDRA-1072, please see that issue for more details and context.
> This issue essentially has two parts.
> * One that sends along the operation type to the receiving node.
> * The second part moves the sstable recovery code out of SSTableWriter and into a new class, making it easy to add on other recovery processes.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.