Jon Haddad commented on CASSANDRA-13853:

We shouldn't change the output of schema versions because that already existed 
and people might be parsing it.

Since this is going into 4.0, is meant to be human readable, and we already 
have a programmatic means of getting this info (jmx), I'm OK with breaking 
changes if they are an improvement to it's readability.  

Yes, people are parsing nodetool.  It's a bummer.  On the upside, I think that 
virtual tables will be able to take over most of the duty of programmatic 
interface with the DB. 

> nodetool describecluster should be more informative
> ---------------------------------------------------
>                 Key: CASSANDRA-13853
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13853
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability, Tools
>            Reporter: Jon Haddad
>            Assignee: Preetika Tyagi
>            Priority: Minor
>              Labels: lhf
>             Fix For: 4.x
>         Attachments: cassandra-13853-v5.patch, 
> nodetool_describecluster_test.py
> Additional information we should be displaying:
> * Total node count
> * List of datacenters, RF, with number of nodes per dc, how many are down, 
> * Version(s)

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to