[
https://issues.apache.org/jira/browse/CASSANDRA-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284206#comment-14284206
]
Eugene commented on CASSANDRA-7950:
-----------------------------------
Might be worth looking into how the column command does it. e.g.:
cat /proc/meminfo
cat /proc/meminfo | column -t
At the very least if these nodetool commands had proper delimitation (a single
space between fields) their output could be easily parsed by utilities and the
column command could be used manually to correct the output.
> 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
> Priority: Minor
> Labels: lhf
> Fix For: 2.0.13
>
> Attachments: 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)
