[
https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17563308#comment-17563308
]
Ekaterina Dimitrova commented on CASSANDRA-15254:
-------------------------------------------------
FYI - I opened and linked to this ticket CASSANDRA-17734. to validate that
Config properties actually are always updated internally so that we see and
update properly in Settings Virtual Table when this patch lands. I found
examples where JMX updates properly Cassandra and shows the right value
assigned internally but this is not assigned to the original Config class
property and we just see and operate with the yaml property. In this case
update to that one from Settings Table would have had zero effect internally.
> 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: Benjamin Lerer
> Priority: Normal
>
> 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]
