[
https://issues.apache.org/jira/browse/CASSANDRA-19393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817305#comment-17817305
]
Stefan Miklosovic commented on CASSANDRA-19393:
-----------------------------------------------
I am on the edge if we should do this or not. While it does make sense to group
this, there is some kind of a habit in nodetool that each command is
standalone. Is there any precedent in nodetool which would do it like you
suggest?
Also, there is a lot of references in the tests which use existing commands.
You will need to fix all the tests which are calling the existing commands and
change them.
> Introduce nodetool command to dump cluster metadata
> ---------------------------------------------------
>
> Key: CASSANDRA-19393
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19393
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
> Reporter: n.v.harikrishna
> Assignee: n.v.harikrishna
> Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Adding a nodetool command for dumping cluster metadata would be handy when
> compared to making a JMX call. Nodetool has two more commands related to
> cluster metadata service (describecms and reconfigurecms). These commands can
> be grouped for simplicity.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
