Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-1331

dfs -test should work like /bin/test

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 0.20.2, 2.0.2-alpha, 3.0.0-alpha1
    • Fix Version/s: 2.0.3-alpha
    • Component/s: tools
    • Labels:
      None
    • Hadoop Flags:
      Incompatible change, Reviewed
    • Release Note:
      "test" will not print a warning for non-existent paths when testing for existence

      Description

      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?

        Attachments

        1. hdfs1331-4.txt
          6 kB
          Andy Isaacson
        2. hdfs1331-3.txt
          5 kB
          Andy Isaacson
        3. hdfs1331-2.txt
          5 kB
          Andy Isaacson
        4. hdfs1331-with-hadoop8994.txt
          6 kB
          Andy Isaacson
        5. hdfs1331.txt
          5 kB
          Andy Isaacson

          Issue Links

            Activity

              People

              • Assignee:
                adi2 Andy Isaacson
                Reporter:
                aw Allen Wittenauer
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: