[
https://issues.apache.org/jira/browse/CASSANDRA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237033#comment-13237033
]
Sam Tunnicliffe commented on CASSANDRA-3937:
--------------------------------------------
The attached patch contains the trivial implementation. A couple of questions
occurred to me though...
Firstly, is prepending the schema version string onto the existing output
likely to break any existing tooling ? If so, it'd be better to append it
instead, the reason I didn't do that in the first place was purely aesthetic -
seemed to scan better with the schema info first.
Secondly, StorageProxy.decribeSchemaVersions() messages all live nodes in the
ring to find out their Schema versions. I thought that maybe this might be a
useful thing to expose via nodetool. Are there objections to adding nodetool
commands that require network comms?
> nodetool describering should report the schema version
> ------------------------------------------------------
>
> Key: CASSANDRA-3937
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3937
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Brandon Williams
> Priority: Trivial
> Labels: lhf
> Fix For: 1.1.0
>
> Attachments:
> v1-0001-CASSANDRA-3937-Add-schema-version-to-nodetool-describe.txt
>
>
> Specifically to aid in debugging things like CASSANDRA-3931, now that you
> can't just decode the UUIDs to see which one has the higher timestamp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
