[ https://issues.apache.org/jira/browse/HDFS-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489416#comment-13489416 ]
Daryn Sharp commented on HDFS-1331: ----------------------------------- Sorry for the delay. A very small request is to follow the pattern for the usage of other commands by displaying each option on a separate line like: " -OPT DESCRIPTION\n". > dfs -test should work like /bin/test > ------------------------------------ > > Key: HDFS-1331 > URL: https://issues.apache.org/jira/browse/HDFS-1331 > Project: Hadoop HDFS > Issue Type: Bug > Components: tools > Affects Versions: 0.20.2, 3.0.0, 2.0.2-alpha > Reporter: Allen Wittenauer > Assignee: Andy Isaacson > Priority: Minor > Attachments: hdfs1331-2.txt, hdfs1331.txt, > hdfs1331-with-hadoop8994.txt > > > hadoop dfs -test doesn't act like its shell equivalent, making it difficult > to actually use if you are used to the real test command: > hadoop: > $hadoop dfs -test -d /nonexist; echo $? > test: File does not exist: /nonexist > 255 > shell: > $ test -d /nonexist; echo $? > 1 > a) Why is it spitting out a message? Even so, why is it saying file instead > of directory when I used -d? > b) Why is the return code 255? I realize this is documented as '0' if true. > But docs basically say the value is undefined if it isn't. > c) where is -f? > d) Why is empty -z instead of -s ? Was it a misunderstanding of the man page? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira