Since there is no response / nobody seems to see this as an issue, I am going to remove it (will be removed in 5.0).
________________________________________ From: Miklosovic, Stefan Sent: Wednesday, August 2, 2023 21:57 To: dev@cassandra.apache.org Subject: Removal of commitlog_sync_batch_window_in_ms in 5.0 Hello list, I want to double check this one (1) on ML. It is relatively an innocent low-hanger however the caveat is that it might potentially break the upgrade to 5.0. The deprecation happened in (2) (in 4.0). I think it is just eligible for deletion now. This property was commented out and it is effectively not used. There is even the comment about this (3). Other option is to leave it deprecated. While this might work, I think this is quite a precedence, isn't it? Are there any other configuration parameters we will live with for ever even they are not used? It seems strange to me that we would just keep this one deprecated for good. Do we apply this rule to all other properties from now on then? I am afraid the config would be bloated a little bit after some time ... I think that waiting one major and removing it is a good compromise. (1) https://issues.apache.org/jira/browse/CASSANDRA-17161 (2) https://issues.apache.org/jira/browse/CASSANDRA-13530 (3) https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L545-L546
