[
https://issues.apache.org/jira/browse/CASSANDRA-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288820#comment-14288820
]
Anuja Mandlecha edited comment on CASSANDRA-7950 at 1/23/15 6:03 AM:
---------------------------------------------------------------------
[~brandon.williams]: We will have to definitely add a delimeter option (--
delimeter )to the nodetool command wherein the output will be displayed
seperated by that delimiter and on which cut,grep etc commands can work.
[~aechttpd]: That looks like a good option. Will need to investigate more on
this.
was (Author: anuja_mandlecha):
@Brandon: We will have to definitely add a delimeter option (-- delimeter )to
the nodetool command wherein the output will be displayed seperated by that
delimiter and on which cut,grep etc commands can work.
@Eugene: That looks like a good option. Will need to investigate more on this.
> 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)
