[
https://issues.apache.org/jira/browse/HADOOP-13020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Zhuge resolved HADOOP-13020.
---------------------------------
Resolution: Duplicate
Sorry, missed it in searching for duplicate. Was wondering why nobody reported
such a simple case. Add component {{fs/s3}} to HADOOP-11918 to help duplicate
search.
> 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
>
> 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)
