hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13020) dfs -ls s3a root should not return error when bucket is empty
Date Thu, 14 Apr 2016 10:24:25 GMT

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

Steve Loughran commented on HADOOP-13020:
-----------------------------------------

no worries: I've been known to file duplicates of bugs I've already files. Better to report
than leave out. 

could you do a build of 2.8 and verify the command works there?

> dfs -ls s3a root should not return error when bucket is empty
> -------------------------------------------------------------
>
>                 Key: HADOOP-13020
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13020
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 2.6.0
>            Reporter: John Zhuge
>            Assignee: John Zhuge
>            Priority: Trivial
>              Labels: s3
>
> Do not expect {{hdfs dfs -ls}} s3a root to return error "No such file or directory" when
the s3 bucket is empty. Expect no error and empty output, just like listing an empty directory.
> {code}
> $ hdfs dfs -ls s3a://jz-hdfs1/
> Found 1 items
> drwxrwxrwx   -          0 1969-12-31 16:00 s3a://jz-hdfs1/tmp
> $ hdfs dfs -rmdir s3a://jz-hdfs1/tmp
> $ hdfs dfs -ls s3a://jz-hdfs1/
> ls: `s3a://jz-hdfs1/': No such file or directory
> {code}



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

Mime
View raw message