[
https://issues.apache.org/jira/browse/CASSANDRA-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17447275#comment-17447275
]
Benjamin Lerer commented on CASSANDRA-15254:
--------------------------------------------
[~dcapwell] The patch I was working on took care of unifying the data logged by
Config and exposed by the VirtualTable is was also taking into account sensible
data through some new annotation and ignoring deprecated config settings. That
approach was based on fields, which up to now where supposed to be always
public (that used to be the convention for config fields). I did not realized
that we intended to change that. May be we should also discuss this point in
the current on going dev discussion.
Once we have a clear vision of where the project wish to go with the
configuration. I can come back to the patches and cook a new one keeping all
the relevant bits and pieces from them :-)
> 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.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
