hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-1331) dfs -test should work like /bin/test
Date Tue, 11 Jan 2011 23:02:49 GMT

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

Allen Wittenauer updated HDFS-1331:
-----------------------------------

    Issue Type: Bug  (was: Improvement)

I'm changing this back to a bug.

The way test works is not expected behavior from anyone who has actually done any real shell
coding.

> 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
>            Reporter: Allen Wittenauer
>            Priority: Minor
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message