[
https://issues.apache.org/jira/browse/HADOOP-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097038#comment-14097038
]
Daryn Sharp commented on HADOOP-7713:
-------------------------------------
I agree, and I'm perfectly fine with headers being default on trunk. I just
don't want an incompatibility in 2.x that might be disruptive to deployment,yet
I want the option because it's a pain to remember which field is which. :)
> 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: HADOOP-7713.patch, HADOOP-7713.patch, HADOOP-7713.patch,
> HADOOP-7713.patch, HADOOP-7713.patch, HADOOP-7713.patch, HADOOP-7713.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 was sent by Atlassian JIRA
(v6.2#6252)
