cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5053) not possible to change crc_check_chance
Date Tue, 11 Dec 2012 16:31:21 GMT

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

Jonathan Ellis commented on CASSANDRA-5053:
-------------------------------------------

Moving it from per-CF to global seems kind of backwards, don't you think?  The overwhelming
tendency has been for people to push for more fine-grained control over things.
                
> not possible to change crc_check_chance
> ---------------------------------------
>
>                 Key: CASSANDRA-5053
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5053
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.1.1, 1.1.7
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>            Priority: Minor
>             Fix For: 1.1.7
>
>         Attachments: 0001-fix-CASSANDRA-5053-not-possible-to-change-crc_check_.patch
>
>
> It is not possible to change crc_check_chance using a schema modification after CASSANDRA-4266
> This patch fixes that and moves the setting out into a configuration parameter instead,
you dont want to upgrade/scrub/.. all your sstables to change the crc_check_chance.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message