[
https://issues.apache.org/jira/browse/CASSANDRA-19957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887716#comment-17887716
]
Stefan Miklosovic commented on CASSANDRA-19957:
-----------------------------------------------
Do we want to drive this via nodetool? My perception is that adding more and
more subcommands is not optimal and we try to do it via CQL instead. There
might be e.g. a virtual table controlling it. In the future, we might make this
configuration transactional via TCM so by setting it on one node via CQL it
would be automatically visible on all nodes and configured accordingly. I do
not think putting more commands / base it on JMX is desirable. If you are a
poweruser just keep jmx methods there and you can call them manually instead of
via nodetool.
> Nodetool support to get and set the authenticator and authorizer
> ----------------------------------------------------------------
>
> Key: CASSANDRA-19957
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19957
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
> Reporter: Ayushi Singh
> Assignee: Ayushi Singh
> Priority: Normal
>
> Add {{nodetool}} support in Apache Cassandra to dynamically get and set
> {{authorizer}} and {{authenticator}} configurations. Currently, changes
> require updating the config file and restarting Cassandra. The new commands
> will allow administrators to make updates on-the-fly without a server
> restart, improving flexibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
