[
https://issues.apache.org/jira/browse/CASSANDRA-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141045#comment-14141045
]
Jason Brown commented on CASSANDRA-7978:
----------------------------------------
The patch allows us to set the value when the sstable is opened, but then it's
'fixed' for that sstable for the life of the process, correct? I think we'd
want to be able to change the value live and have it immediately reflected.
Also, as a minor point (probably not worth bothering with), should we stop stop
writing the crc_check_chance into the sstable, as well?
> CrcCheckChance should not be stored as part of an sstable
> ---------------------------------------------------------
>
> Key: CASSANDRA-7978
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7978
> Project: Cassandra
> Issue Type: Improvement
> Reporter: sankalp kohli
> Assignee: T Jake Luciani
> Priority: Minor
> Fix For: 2.0.11
>
> Attachments: 7978.txt
>
>
> CrcCheckChance is stored with compression parameters in the sstable. The only
> way to change it is to do upgrade sstable. I don't see why it should not be a
> hot property.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)