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

Ekaterina Dimitrova updated CASSANDRA-17735:
--------------------------------------------
    Description: 
There are a few problems:

4.0+:
 * the virtual table displays only the cassandra.yaml values for both 
properties, all changes after that are not updated

4.1+:
 *  Breaking compatibility - -1 was considered disabled, this should be 
considered as null now for the new config. The converter should be updated. 
There is a test for the -1, disable but it didn't caught the issue because of 
the previous one mentioned (the disconnect between jmx and the actual property 
in Config class)

  was:
There are a few problems:

4.0+:
 * the virtual table displays only the cassandra.yaml values for both 
properties, all changes after that are not updated

4.1+:

 Breaking compatibility - -1 was considered disabled, this should be considered 
as null now for the new config. The converter should be updated. There is a 
test for the -1, disable but it didn't caught the issue because of the previous 
one mentioned (the disconnect between jmx and the actual property in Config 
class)


> Fix issues with index_summary_resize_interval and index_summary_capacity
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17735
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17735
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local/Config
>            Reporter: Ekaterina Dimitrova
>            Assignee: Ekaterina Dimitrova
>            Priority: Low
>             Fix For: 4.0.x, 4.1-beta, 4.x
>
>
> There are a few problems:
> 4.0+:
>  * the virtual table displays only the cassandra.yaml values for both 
> properties, all changes after that are not updated
> 4.1+:
>  *  Breaking compatibility - -1 was considered disabled, this should be 
> considered as null now for the new config. The converter should be updated. 
> There is a test for the -1, disable but it didn't caught the issue because of 
> the previous one mentioned (the disconnect between jmx and the actual 
> property in Config class)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to