[
https://issues.apache.org/jira/browse/CASSANDRA-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080126#comment-13080126
]
Pavel Yaskevich commented on CASSANDRA-1717:
--------------------------------------------
By special-casing i mean the following:
bq. We would say "no mmap" with compression and no checksum without
compression, but you have the "compression with no-op algorithm". This has my
preference as said previously, but we must be aware that people will ask why we
have a non-mmap non compressed mode and a compressed no-op mode (we cannot
really get rid of the first one because otherwise we say "you shall use mmap
forever now").
bq. But I'm pretty sure that after 1.0 we'll make compression the default. So I
don't want to add a lot of complexity for uncompressed sstables.
In that case can we consider making that compression only feature instead of
banging our heads against the wall trying to come up with solution for
non-compressed data?
> 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: 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
