[
https://issues.apache.org/jira/browse/HADOOP-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095803#comment-14095803
]
Daryn Sharp commented on HADOOP-7713:
-------------------------------------
Like the other count jira, this would be great to have in 2.x. I know we have
various SE and customer monitoring scripts that depend on this command, so I'd
rather not have the headers by default so we don't have to hunt down everyone
using the command.
I think the header field names in count's former help message are probably a
better choice than the new ones in this patch. I don't mind the upper/lower
case so much as fields that contain spaces. I often like to write utilities
that split a header and use them as map keys. Spaces in the header fields
thwarts that.
I'd suggest using a single letter for the header option (maybe v(erbose)) to be
inline with the other commands. Otherwise it will thwart the "one of these
days" feature of allowing option bundling. Multi-char options are better
implemented as "--opt".
> 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)
