[
https://issues.apache.org/jira/browse/HADOOP-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-13674:
-----------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.8.0
Status: Resolved (was: Patch Available)
Pre-commit has given a +1, and I have confirmed a full test run passes against
US-west-2. I have committed this to trunk, branch-2 and branch-2.8. Steve,
thank you for the code review.
> S3A can provide a more detailed error message when accessing a bucket through
> an incorrect S3 endpoint.
> -------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-13674
> URL: https://issues.apache.org/jira/browse/HADOOP-13674
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Minor
> Fix For: 2.8.0
>
> Attachments: HADOOP-13674-branch-2.001.patch,
> HADOOP-13674-branch-2.002.patch
>
>
> When accessing the S3 service through a region-specific endpoint, the bucket
> must be located in that region. If the client attempts to access a bucket
> that is not located in that region, then the service replies with a 301
> redirect and the correct region endpoint. However, the exception thrown by
> S3A does not include the correct endpoint. If we included that information
> in the exception, it would make it easier for users to diagnose and fix
> incorrect configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
