[
https://issues.apache.org/jira/browse/CASSANDRA-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anuja Mandlecha updated CASSANDRA-7950:
---------------------------------------
Attachment: 7950.patch
[~eugenstud]: I looked into how column command in unix works and did the same
for compactionhistory command and also added TAB (\t) as a delimeter for now
which can be used by grep, cut,awk commands. In future we can also provide a
delimeter option as I have mentioned earlier.
For compactionstats the code is already present to calculate the
maxColumnLength, hence I only added a delimeter TAB(\t) to it. The attached
path contain these changes.
Note: I have used cassandra 2.1 branch.
> 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: 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)
