hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13674) S3A can provide a more detailed error message when accessing a bucket through an incorrect S3 endpoint.
Date Tue, 18 Oct 2016 22:07:00 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Wang updated HADOOP-13674:
---------------------------------
    Fix Version/s: 3.0.0-alpha2

> 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, 3.0.0-alpha2
>
>         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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message