[
https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684536#comment-17684536
]
Benjamin Lerer commented on CASSANDRA-15254:
--------------------------------------------
Just to make sure that we have all the same understanding. The plan is only to
allow setting the properties that can be set dynamically today (which is a
small sub-set of the properties), right? I have not checked but it might be
possible that some setter or getters are actually not used by JMX.
[~mmuzaf] Your schema mention Auto-Generated classes which is a good idea. I am
simply not sure that it is feasible in practice as setting the property is also
often only a minor part of the logic involved in changing a configuration.
Configuration are often use at start up to initialize some C* components and in
case of configuration update that component somehow need to be modified in a
non generic way. Up to now that logic was performed in the different JMX
implementation classes. Each of them was usually setting the config parameter
and then updating the impacted component that they were managing.
> Allow UPDATE on settings virtual table to change running configurations
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-15254
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15254
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Virtual Tables
> Reporter: Chris Lohfink
> Assignee: Maxim Muzafarov
> Priority: Normal
> Attachments: Configuration Registry Diagram.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Allow using UPDATE on the system_views.settings virtual table to update
> configs at runtime for the equivalent of the dispersed JMX
> attributes/operations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
