Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 7 Oct 2014 22:59:33 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12741999.1410912425000.213251.1412722773841@Atlassian.JIRA>
In-Reply-To: <JIRA.12741999.1410912425000@Atlassian.JIRA>
References: <JIRA.12741999.1410912425000@Atlassian.JIRA>
 <JIRA.12741999.1410912425465@arcas>
Subject: [jira] [Updated] (CASSANDRA-7950) Output of nodetool
 compactionstats and compactionhistory does not work well with long keyspace
 and column family names.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-7950:
-----------------------------------------
    Fix Version/s:     (was: 2.0.6)
                   2.0.11

> 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
>             Fix For: 2.0.11
>
>         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)