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

Ekaterina Dimitrova updated CASSANDRA-17161:
--------------------------------------------
    Description: 
commitlog_sync_batch_window_in_ms is deprecated in 4.0 and has to be removed in 
5.0

This will require also some work around the in-jvm upgrade tests.

Currently they do not work if we remove a parameter in a later version.

Side note: They also don't work if we change the type of the parameter in 
Config class in a newer Cassandra version. If you plan to set it in the tests 
themselves, it won't work. If you change the type but your don't set the 
parameter, no issue so there might be some workaround solution instead of 
working on the dtest framework itself.... TBD

  was:
commitlog_sync_batch_window_in_ms is deprecated in 4.0 and has to be removed in 
5.0

This will require also some work around the in-jvm upgrade tests.

Currently they do not work if we remove a parameter in a later version.

Side note: They also don't work if we change the type of the parameter in 
Config class in a newer Cassandra version. 


> Remove commitlog_sync_batch_window_in_ms
> ----------------------------------------
>
>                 Key: CASSANDRA-17161
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17161
>             Project: Cassandra
>          Issue Type: Task
>          Components: Build
>            Reporter: Ekaterina Dimitrova
>            Priority: Normal
>             Fix For: 5.x
>
>
> commitlog_sync_batch_window_in_ms is deprecated in 4.0 and has to be removed 
> in 5.0
> This will require also some work around the in-jvm upgrade tests.
> Currently they do not work if we remove a parameter in a later version.
> Side note: They also don't work if we change the type of the parameter in 
> Config class in a newer Cassandra version. If you plan to set it in the tests 
> themselves, it won't work. If you change the type but your don't set the 
> parameter, no issue so there might be some workaround solution instead of 
> working on the dtest framework itself.... TBD



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

Reply via email to