Return-Path: 
 <common-issues-return-24570-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id BD327B6EA
	for <apmail-hadoop-common-issues-archive@minotaur.apache.org>;
 Mon,  2 Jan 2012 06:21:59 +0000 (UTC)
Received: (qmail 76375 invoked by uid 500); 2 Jan 2012 06:21:59 -0000
Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org
Received: (qmail 75506 invoked by uid 500); 2 Jan 2012 06:21:55 -0000
Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-issues@hadoop.apache.org>
List-Id: <common-issues.hadoop.apache.org>
Reply-To: common-issues@hadoop.apache.org
Delivered-To: mailing list common-issues@hadoop.apache.org
Received: (qmail 75482 invoked by uid 99); 2 Jan 2012 06:21:54 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jan 2012 06:21:54 +0000
X-ASF-Spam-Status: No, hits=-2001.6 required=5.0
	tests=ALL_TRUSTED,RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jan 2012 06:21:52 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id C5E52134715
	for <common-issues@hadoop.apache.org>; Mon,  2 Jan 2012 06:21:30 +0000 (UTC)
Date: Mon, 2 Jan 2012 06:21:30 +0000 (UTC)
From: "Harsh J (Commented) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1135849626.57382.1325485290811.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-7713) dfs -count -q should label output
 column
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/HADOOP-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178297#comment-13178297 ] 

Harsh J commented on HADOOP-7713:
---------------------------------

+1 for the change. Would you mind updating docs for this as well?
                
> dfs -count -q should label output column
> ----------------------------------------
>
>                 Key: HADOOP-7713
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7713
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Nigel Daley
>            Assignee: Jonathan Allen
>            Priority: Trivial
>              Labels: newbie
>         Attachments: HDFS-364.patch, HDFS-364.patch
>
>
> These commands should label the output columns:
> {code}
> hadoop dfs -count <dir>...<dir>
> hadoop dfs -count -q <dir>...<dir>
> {code}
> Current output of the 2nd command above:
> {code}
> % hadoop dfs -count -q /user/foo /tmp
>         none             inf         9569         9493         6372553322 hdfs://nn1.bar.com/user/foo
>         none             inf          101         2689       209349812906 hdfs://nn1.bar.com/tmp
> {code}
> It is not obvious what these columns mean.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira