[
https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688113#comment-17688113
]
Maxim Muzafarov commented on CASSANDRA-15254:
---------------------------------------------
[~dcapwell] thank you! I think we are on the same page for now, I'll prepare PR
according to everything we discussed here.
Of course, the JMX itself remains unchanged. I mean, some kind of refactoring
needs to be done to handle the configuration changes for some of the Config's
properties that might perform actions before and after changing the property
value and make them handled for the same things by onBeforeChange,
onAfterChange listener calls. Of course, I don't know the number of changes as
we have about 345 configuration fields to check, so I suggested breaking the
patch into small ones. I will check the details and get back here.
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
