[
https://issues.apache.org/jira/browse/CASSANDRA-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730579#comment-14730579
]
Eugene commented on CASSANDRA-7950:
-----------------------------------
Thank you to everyone that has worked on this so far.
Will this, by chance, also fix the output of other commands, for example
`nodetool listsnapshots`?
I created a snapshot with a long tag
(some-really-long-snapshot-name-geezey-petes). Ended up with the following:
{code}
# nodetool listsnapshots
Snapshot Details:
Snapshot name Keyspace name Column family name
True size Size on disk
some-really-long-snapshot-name-geezey-petesgalactaron
replicatorstide 0 bytes 570.68 MB
some-really-long-snapshot-name-geezey-petesdse_system leases
0 bytes 13 bytes
some-really-long-snapshot-name-geezey-petesdse_system
real_leaders 0 bytes 13 bytes
some-really-long-snapshot-name-geezey-petesdse_system
encrypted_keys 0 bytes 13 bytes
some-really-long-snapshot-name-geezey-petesdse_system
registered_leaders 0 bytes 13 bytes
{code}
> Output of nodetool compactionstats and compactionhistory does not work well
> with long keyspace and column family names.
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-7950
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7950
> Project: Cassandra
> Issue Type: Bug
> Environment: CentOS 5, 64bit, Oracle JDK 7, DSE
> Reporter: Eugene
> Assignee: Michael Shuler
> Priority: Minor
> Labels: lhf
> Fix For: 2.1.x
>
> Attachments: 7950.patch, nodetool-examples.txt
>
>
> When running these commands:
> nodetool compactionstats
> nodetool compactionhistory
> The output can be difficult to grok due to long keyspace names, column family
> names, and long values. I have attached an example.
> It's difficult for both humans and grep/sed/awk/perl to read.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
