hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mukund Madhugiri (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2195) dfs mkdir command differs from POSIX standards
Date Tue, 13 Nov 2007 00:16:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541999

Mukund Madhugiri commented on HADOOP-2195:

for the first case, it needs to be documented that it follows mkdir -p. The du command documents
it when help for the du command is displayed.

mkdir currently does not display what semantics it follows:
 bin/hadoop dfs -help mkdir
-mkdir <path>:  Create a directory in specified location. 

whereas du shows this:
 bin/hadoop dfs -help du
-du <path>:     Show the amount of space, in bytes, used by the files that 
                match the specified file pattern.  Equivalent to the unix
                command "du -sb <path>/*" in case of a directory, 
                and to "du -b <path>" in case of a file.
                The output is in the form 
                        name(full path) size (in bytes)

> dfs mkdir command differs from POSIX standards
> ----------------------------------------------
>                 Key: HADOOP-2195
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2195
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.15.1, 0.16.0
>            Reporter: Mukund Madhugiri
>             Fix For: 0.16.0
> Assuming the dfs commands follow POSIX standards, there are some problems with the DFS
mkdir command. I compared the DFS output with that of RHEL 4u5:
> 1. mkdir a directory that exists:
> Linux: mkdir: cannot create directory `test': File exists
> DFS: No output
> 2. mkdir a directory with the name of a file that already exists:
> - Linux: mkdir: `test/one' exists but is not a directory
> - DFS: mkdir: java.io.IOException: Invalid directory name: <home directory>/test/one

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message