[
https://issues.apache.org/jira/browse/CASSANDRA-17160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470972#comment-17470972
]
Ekaterina Dimitrova commented on CASSANDRA-17160:
-------------------------------------------------
Thank you [~maedhroz], I just applied the patch on the latest 4.0 and trunk
branches and started CI. I will commit on green CI (from this patch point of
view green...)
[4.0|
https://github.com/ekaterinadimitrova2/cassandra/commit/161566c2c8437f6f52c6aff01cced6fafbe375f5]
| [Jenkins| https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1353/]
[trunk| https://github.com/ekaterinadimitrova2/cassandra/commits/17160-trunk] |
[Jenkins |https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1354/]
> Emit warnings for deprecated parameters (changed names) only once
> -----------------------------------------------------------------
>
> Key: CASSANDRA-17160
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17160
> Project: Cassandra
> Issue Type: Improvement
> Components: Build
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Low
> Fix For: 4.0.x, 4.x
>
>
> We added backward compatibility for two config parameters in CASSANDRA-17141
> to fix a bug but I realized that with the current setup, a warning for
> deprecated parameter can be logged more than once which is not needed and
> only introduces noise to the logs.
> I already fixed that in CASSANDRA-15234 where this would lead to a lot of
> warnings and it is easy to spot. I will backport the tiny fix here too in
> case we add more parameters, etc; to prevent the potential noise.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
