[
https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695831#comment-17695831
]
David Capwell commented on CASSANDRA-15254:
-------------------------------------------
Awesome, thanks so much for all this hard work!
As far as I can tell, this is the scope of this work
* have a way to define mutable or not (dev@ looks to prefer annotation, name is
flexible)
* have a way to listen to changes (subset of mutable configs trigger logic on
JMX change; current patch highlights this problem)
* have a way to go from Type -> String -> Type; current patch has String ->
Type but relies on Object::toString which may differ
* config validation consistency; for any mutable configs, if there is logic to
validate it it should also happen in the vtable. Many cases rely on type to do
this but for any case done in DatabaseDescriptor a solution is needed
[~mmuzaf] let me know if this is your thinking as well. I hope non of this is
a surprise as I believe your patch attempts to address these issues, but just
trying to flesh out the scope
> 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: 40m
> 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]
