You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2021/11/17 20:13:00 UTC
[jira] [Updated] (CASSANDRA-17160) Emit warnings for deprecated parameters (changed names) only once
[ https://issues.apache.org/jira/browse/CASSANDRA-17160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ekaterina Dimitrova updated CASSANDRA-17160:
--------------------------------------------
Change Category: Operability
Complexity: Low Hanging Fruit
Component/s: Build
Fix Version/s: 4.0.x
Assignee: Ekaterina Dimitrova
Priority: Low (was: Normal)
Status: Open (was: Triage Needed)
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org