[
https://issues.apache.org/jira/browse/CASSANDRA-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-808:
-------------------------------------
Fix Version/s: 0.8
(was: 0.7)
Let's push data format change to 0.8. I'm burned out on it, and nobody else is
stepping up to help review.
We can fix CASSANDRA-16 with the current data format for 0.7.
> Need a way to skip corrupted data in SSTables
> ---------------------------------------------
>
> Key: CASSANDRA-808
> URL: https://issues.apache.org/jira/browse/CASSANDRA-808
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Stu Hood
> Priority: Minor
> Fix For: 0.8
>
>
> The new SSTable format will allow for checksumming of the data file, but as
> it stands, we don't have a better way to handle the situation than throwing
> an Exception indicating that the data is unreadable.
> We might want to add an option (triggerable via a command line flag?) to
> Cassandra that will allow for skipping of corrupted keys/blocks in SSTables,
> to pretend they don't exist rather than throwing the Exception.
> An administrator could temporarily enable the option and trigger a compaction
> to perform a local repair of data, or they could leave it enabled constantly
> for hands-off recovery.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
