[
https://issues.apache.org/jira/browse/HADOOP-13516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427854#comment-15427854
]
Steve Loughran commented on HADOOP-13516:
-----------------------------------------
I'll see if I can replicate this.
All work is going to have to be against branch-2 or trunk; there's been a lot
of changes to s3a there and things won't work.
Interesting that you were getting a 403 there; could be a sign of some
regression —we've been doing a lot with provider plugin, session providers, etc.
Can you get set up for running the hadoop-aws test run? Ask for help on the
common-dev list if you need it —hopefully everything you need is written up in
https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md
if
> Listing an empty s3a NON root directory throws FileNotFound.
> ------------------------------------------------------------
>
> Key: HADOOP-13516
> URL: https://issues.apache.org/jira/browse/HADOOP-13516
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Affects Versions: 2.7.0
> Reporter: Shaik Idris Ali
> Assignee: Steve Loughran
> Priority: Minor
>
> With an empty s3 bucket and run
> {code}
> $ hadoop fs -D... -ls s3a://hdfs-s3a-test/emptyDirectory
> 15/05/04 15:21:34 WARN util.NativeCodeLoader: Unable to load native-hadoop
> library for your platform... using builtin-java classes where applicable
> ls: `s3a://hdfs-s3a-test/emtpyDirectory': No such file or directory
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
