cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7978) CrcCheckChance should not be stored as part of an sstable
Date Fri, 19 Sep 2014 21:20:35 GMT

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

Benedict commented on CASSANDRA-7978:
-------------------------------------

We only need to set the value wherever it's retrieved from, and call FileCacheService.invalidate()
on each of the files we've changed the setting for.

I'd kind of prefer, if we want to make this setting configurable live, to drop maintenance
of the setting from compression metadata and just fetch it from the CFMetaData each time we
open a reader.

> 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)

Mime
View raw message