cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5822) Keep previous index_interval value when upgrading to 2.0
Date Mon, 29 Jul 2013 19:47:49 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yuki Morishita updated CASSANDRA-5822:
--------------------------------------

    Attachment: 5822-v2.txt

v2 removed index_interval from cassandra.yaml as it is.

Also, I modified the place to set value from cassandra.yaml, because system tables' index_interval
can never be updated once set. So no matter what value you set for index_interval in cassandra.yaml,
system tables always use the default of 128 index_interval.
                
> Keep previous index_interval value when upgrading to 2.0
> --------------------------------------------------------
>
>                 Key: CASSANDRA-5822
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5822
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 2.0 beta 2
>            Reporter: Yuki Morishita
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: 5822.txt, 5822-v2.txt
>
>
> 2.0 moves index_interval from global to CF level, but current beta always sets default
of 128 to existing CFs from previous versions.
> I think it is better (and not surprising) to keep index_interval in cassandra.yaml and
use that as default for existing CF.

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