[
https://issues.apache.org/jira/browse/CASSANDRA-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16321804#comment-16321804
]
Jeff Jirsa commented on CASSANDRA-14162:
----------------------------------------
[~iamaleksey] / [~slebresne] / [~jjordan] - The only argument against such a
backport seems like "it may break someone's tool parsing" (if someone's relying
on some specifics of the old, awkward nodetool output). Is that something we
typically protect against in minor versions?
> Backport 7950
> -------------
>
> Key: CASSANDRA-14162
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14162
> Project: Cassandra
> Issue Type: Bug
> Reporter: Kurt Greaves
> Assignee: Kurt Greaves
> Priority: Minor
> Fix For: 3.0.16
>
> Attachments: 14162-3.0.patch, Screenshot from 2018-01-11
> 01-02-02.png, Screenshot from 2018-01-11 01-02-46.png, Screenshot from
> 2018-01-11 01-02-51.png
>
>
> Colleagues have had issues with output of listsnapshots/compactionstats
> because of things with really long names. Mostly cosmetic but I see no reason
> we shouldn't backport CASSANDRA-7950 to 3.0. It's practically a bugfix. I've
> attached a patch and a bunch of images to show the relevant commands working
> as intended after applying the patch.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
