You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Andres de la Peña (Jira)" <ji...@apache.org> on 2022/02/02 15:57:00 UTC

[jira] [Created] (CASSANDRA-17341) Merge guardrails and track warnings configurations

Andres de la Peña created CASSANDRA-17341:
---------------------------------------------

             Summary: Merge guardrails and track warnings configurations
                 Key: CASSANDRA-17341
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17341
             Project: Cassandra
          Issue Type: Task
          Components: Feature/Guardrails, Local/Config
            Reporter: Andres de la Peña
            Assignee: Andres de la Peña


As discussed in CASSANDRA-17148, a first step for the integration between guardrails and track warnings is merging their configurations, which are almost identical. This ticket would cover merging their config sections in {{cassandra.yaml}} and their corresponding JMX getters and setters. A tighter integration between the internals of both features wouldn't be part of this ticket, but of either CASSANDRA-17148 or a new subtask of it.

Neither guardrails nor track warnings have included in any release, so it would be desirable to do this before releasing 4.1 so we don't have to deprecate properties.

There's an ongoing discussion about refactoring {{cassandra.yaml}} spread across CASSANDRA-17292, CASSANDRA-17188 and CASSANDRA-17212. I understand that any change affecting the config for guardrails also affects the config track warnings, because they are almost identical. Thus, I think that merging both config sections would ease any refactoring plan that is agreed on that discussion.



--
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