Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <256438068.546701267160307832.JavaMail.jira@brutus.apache.org>
Date: Fri, 26 Feb 2010 04:58:27 +0000 (UTC)
From: "Eric Evans (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Updated: (CASSANDRA-808) Need a way to skip corrupted data
 in SSTables
In-Reply-To: <2118789135.369791266529527908.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Evans updated CASSANDRA-808:
---------------------------------

    Attachment: v1-0003-consistent-column-and-supercolumn-convenience-funcs.txt
                v1-0002-add-new-test_insert_super-func-test-for-avro.txt
                v1-0001-CASSANDRA-808-better-get_api_version-func-test-for-avr.txt

> 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
>             Fix For: 0.7
>
>         Attachments: v1-0001-CASSANDRA-808-better-get_api_version-func-test-for-avr.txt, v1-0002-add-new-test_insert_super-func-test-for-avro.txt, v1-0003-consistent-column-and-supercolumn-convenience-funcs.txt
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.