hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Takenori Sato (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-11742) mkdir by file system shell fails on an empty bucket
Date Tue, 24 Mar 2015 04:47:53 GMT
Takenori Sato created HADOOP-11742:
--------------------------------------

             Summary: mkdir by file system shell fails on an empty bucket
                 Key: HADOOP-11742
                 URL: https://issues.apache.org/jira/browse/HADOOP-11742
             Project: Hadoop Common
          Issue Type: Bug
          Components: fs/s3
         Environment: CentOS 7
            Reporter: Takenori Sato


I have built the latest 2.7, and tried S3AFileSystem.

Then found that _mkdir_ fails on an empty bucket, named *s3a* here, as follows:

{code}
# hadoop-2.7.0-SNAPSHOT/bin/hdfs dfs -mkdir s3a://s3a/foo
15/03/24 03:49:35 DEBUG s3a.S3AFileSystem: Getting path status for s3a://s3a/foo (foo)
15/03/24 03:49:36 DEBUG s3a.S3AFileSystem: Not Found: s3a://s3a/foo
15/03/24 03:49:36 DEBUG s3a.S3AFileSystem: Getting path status for s3a://s3a/ ()
15/03/24 03:49:36 DEBUG s3a.S3AFileSystem: Not Found: s3a://s3a/
mkdir: `s3a://s3a/foo': No such file or directory
{code}

So does _ls_.

{code}
# hadoop-2.7.0-SNAPSHOT/bin/hdfs dfs -ls s3a://s3a/
15/03/24 03:47:48 DEBUG s3a.S3AFileSystem: Getting path status for s3a://s3a/ ()
15/03/24 03:47:48 DEBUG s3a.S3AFileSystem: Not Found: s3a://s3a/
ls: `s3a://s3a/': No such file or directory
{code}

This is how it works via s3n.

{code}
# hadoop-2.7.0-SNAPSHOT/bin/hdfs dfs -ls s3n://s3n/
# hadoop-2.7.0-SNAPSHOT/bin/hdfs dfs -mkdir s3n://s3n/foo
# hadoop-2.7.0-SNAPSHOT/bin/hdfs dfs -ls s3n://s3n/
Found 1 items
drwxrwxrwx   -          0 1970-01-01 00:00 s3n://s3n/foo
{code}

The snapshot is the following:

{quote}
\# git branch
\* branch-2.7
  trunk
\# git log
commit 929b04ce3a4fe419dece49ed68d4f6228be214c1
Author: Harsh J <harsh@cloudera.com>
Date:   Sun Mar 22 10:18:32 2015 +0530
{quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message