[jira] Commented: (CASSANDRA-1717) Cassandra cannot detect corrupt-but-readable column data

["Stu Hood (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929223#action_12929223 ] 

Stu Hood commented on CASSANDRA-1717:
-------------------------------------

I think we should consider delaying this until #16 is fixed (hopefully in 0.8): adding compression will require a block based format, which is a natural level to checksum at. Additionally, if a user wanted to force corruption detection per lookup (as opposed to only when the entire block is read) GZIPs built checksumming kills two birds with one stone.

> Cassandra cannot detect corrupt-but-readable column data
> --------------------------------------------------------
>
>                 Key: CASSANDRA-1717
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1717
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>             Fix For: 0.7.1
>
>         Attachments: checksums.txt
>
>
> Most corruptions of on-disk data due to bitrot render the column (or row) unreadable, so the data can be replaced by read repair or anti-entropy.  But if the corruption keeps column data readable we do not detect it, and if it corrupts to a higher timestamp value can even resist being overwritten by newer values.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.