hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8496) FsShell is broken with s3 filesystems
Date Thu, 21 Jun 2012 16:05:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398513#comment-13398513
] 

Alejandro Abdelnur commented on HADOOP-8496:
--------------------------------------------

Daryn, no '-s0' entry.

Using Hadoop 1.0.1 things works:

{code}
$ bin/hadoop fs -conf ~/aws-s3.xml -ls s3n://tucu/
Found 4 items
-rwxrwxrwx   1          5 2012-06-08 14:00 /foo.txt
drwxrwxrwx   -          0 1969-12-31 16:00 /test
-rwxrwxrwx   1          5 2012-06-08 13:53 /test.txt
-rwxrwxrwx   1          5 2012-06-08 13:56 /test1.txt
$ 
{code}

Using Hadoop 2.0.0/trunk things fail:

{code}
$ bin/hadoop fs -conf ~/aws-s3.xml -ls s3n://tucu/
Found 4 items
-ls: -0s
Usage: hadoop fs [generic options] -ls [-d] [-h] [-R] [<path> ...]
$ 
{code}

                
> FsShell is broken with s3 filesystems
> -------------------------------------
>
>                 Key: HADOOP-8496
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8496
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 2.0.1-alpha
>            Reporter: Alejandro Abdelnur
>            Priority: Critical
>
> After setting up a S3 account, configuring the site.xml with the accesskey/password,
when doing an ls on a non-empty bucket I get:
> {code}
> Found 4 items
> -ls: -0s
> Usage: hadoop fs [generic options] -ls [-d] [-h] [-R] [<path> ...]
> {code}
> Note that it correctly shows the number of items in the root of the bucket, it does not
show the contents of the root.
> I've tried -get and -put and it works fine, accessing a folder in the bucket seems to
be fully broken.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message