[ 
https://issues.apache.org/jira/browse/CASSANDRA-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379255#comment-17379255
 ] 

Ekaterina Dimitrova edited comment on CASSANDRA-14162 at 7/12/21, 4:36 PM:
---------------------------------------------------------------------------

As it is only sorted representation, probably it is fine but normally we don't 
backport new behaviors. I think that was the reason also to discuss initially 
whether this patch should be really backported at all. 

Cassandra has that behavior of having pain in the leg wen you slap her in the 
face even after smallest changes, so I felt it's worth mentioning that change 
before any commit. Thank you both


was (Author: e.dimitrova):
As it is only sorted representation, probably it is fine but normally we don't 
backport new behaviors. I think that was the reason also to discuss initially 
whether this patch should be really backported at all. 

Cassandra has that behavior of having pain in the leg wen you slap her in the 
face even after smallest changes, so I felt worth mentioning that change before 
any commit. Thank you both

> Backport 7950 (Output of nodetool compactionstats and compactionhistory does 
> not work well with long keyspace and column family names)
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14162
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14162
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Legacy/Tools
>            Reporter: Kurt Greaves
>            Assignee: Stefan Miklosovic
>            Priority: Low
>             Fix For: 3.0.25
>
>         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
(v8.3.4#803005)

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

Reply via email to