[ https://issues.apache.org/jira/browse/HADOOP-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314779#comment-15314779 ]
Steve Loughran commented on HADOOP-13237: ----------------------------------------- Should we maybe be more relaxed about failures of verifying a bucket exists on startup? I'll try and experiment with downgrading to a warn and seeing what happens to a test run. Irony: we never see this problem in hadoop-aws test runs, because they only run if you have credentials. > s3a initialization against public bucket fails if caller lacks any credentials > ------------------------------------------------------------------------------ > > Key: HADOOP-13237 > URL: https://issues.apache.org/jira/browse/HADOOP-13237 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: 2.8.0 > Reporter: Steve Loughran > Assignee: Steve Loughran > > If an S3 bucket is public, anyone should be able to read from it. > However, you cannot create an s3a client bonded to a public bucket unless you > have some credentials; the {{doesBucketExist()}} check rejects the call. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org