[
https://issues.apache.org/jira/browse/CASSANDRA-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080441#comment-13080441
]
Sylvain Lebresne commented on CASSANDRA-1717:
---------------------------------------------
bq. In that case can we consider making that compression only feature
For what it's worth, that was basically the idea of having a no-op compression.
Basically we only support compression and if people really really want
something uncompressed with checksum, we give them a compression algorithm that
doesn't compress squat.
Anyway, I'm for "compression only feature" and the no-op compression was just
some idea "in case we need it". We don't even have to do it now. But if someone
asks, it will be trivial to do.
> Cassandra cannot detect corrupt-but-readable column data
> --------------------------------------------------------
>
> Key: CASSANDRA-1717
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1717
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Fix For: 1.0
>
> Attachments: CASSANDRA-1717.patch, 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
