[
https://issues.apache.org/jira/browse/CASSANDRA-17160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468843#comment-17468843
]
Ekaterina Dimitrova commented on CASSANDRA-17160:
-------------------------------------------------
[4.0 patch|https://github.com/ekaterinadimitrova2/cassandra/pull/new/17160-4.0]
| [Jenkins CI run|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1345/]
I will move the ticket to PATCH AVAILABLE when the CI completes to ensure I
didn't break anything random.
The patch is absolutely identical in trunk. I will run CI there pre-commit. In
theory this part was already reviewed for CASSANDRA-15234 but not committed. As
the work from CASSANDRA-15234 will be committed only to trunk, I had to
backport this fix separately.
> 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
>
>
> 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
