[
https://issues.apache.org/jira/browse/HADOOP-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Fabbri updated HADOOP-14013:
----------------------------------
Attachment: HADOOP-14013-HADOOP-13345.001.patch
Attaching v1 patch, based on suggestions from [~steve_l] and [~liuml07].
Also removes example s3guard test settings from the test core-site.xml since we
have the maven profiles now.
Tested via
{noformat}
mvn clean verify -Ddynamo -Ds3guard -Dit.test=ITestS3AAWSCredentialsProvider
-Dtest=none
{noformat}
Without the patch we see the familiar failure:
{noformat}
ITestS3AAWSCredentialsProvider.testAnonymousProvider:132 ยป AWSServiceIO initTa..
{noformat}
With the patch it succeeds, as expected.
> S3Guard: fix multi-bucket integration tests
> -------------------------------------------
>
> Key: HADOOP-14013
> URL: https://issues.apache.org/jira/browse/HADOOP-14013
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: HADOOP-13345
> Reporter: Aaron Fabbri
> Assignee: Aaron Fabbri
> Attachments: HADOOP-14013-HADOOP-13345.001.patch
>
>
> Clone of HADOOP-13876 to address multi-bucket test failures separately.
> One of the issues is with accessing read-only buckets. If a user accesses a
> read-only bucket with credentials that do not have DynamoDB write
> permissions, they will get errors when trying to access the read-only bucket.
> This manifests causes test failures for {{ITestS3AAWSCredentialsProvider}}.
> Goals for this JIRA:
> - Fix {{ITestS3AAWSCredentialsProvider}} in a way that makes sense for the
> real use-case.
> - Document limitations etc. in the s3guard.md site doc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
