[
https://issues.apache.org/jira/browse/CASSANDRA-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001921#comment-13001921
]
David Boxenhorn commented on CASSANDRA-2264:
--------------------------------------------
It would also be nice if we could flip a switch and check all SSTables right
after they are created. This would help us in the case where we are trying to
pinpoint where bad SSTables are entering the system. Also, if this check does
not catch anything, and bad SSTables are created anyway, we will know that the
source of the corruption is exogenous.
I imagine that it would also help in testing prospective Cassandra releases...
> Restore From Snapshot eg: nodetool restore [filename] | ([keyspace]
> [columnfamily])
> -------------------------------------------------------------------------------------
>
> Key: CASSANDRA-2264
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2264
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.7.2
> Reporter: Benjamin Coverston
>
> Store additional metadata in the SSTable including:
> generated_by: (From memtable, compaction, or cleanup)
> ancestors: A list of SSTableNames|MD5sum
> When executed it will copy the ancestors from the snapshot directory to the
> data directory.
> If given Keyspace and ColumnFamily arguments it will attempt to restore all
> SSTables in the Keyspace/Columnfamily on that node.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
