hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HADOOP-15201) Automatically determine region & hence S3 endpoint of buckets
Date Mon, 19 Feb 2018 17:31:00 GMT

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

Steve Loughran resolved HADOOP-15201.
    Resolution: Duplicate

Duplicate of HADOOP-14931, that JIRA wasn't attached to the s3a-uber JIRAs, so I'd missed

> Automatically determine region & hence S3 endpoint of buckets
> -------------------------------------------------------------
>                 Key: HADOOP-15201
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15201
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.0.0
>            Reporter: Steve Loughran
>            Priority: Minor
> Use {{getBucketLocation}} to determine location & map to endpoint, if fs.s3a.endpoint
is set to "automatic"
> S3guard added the API call {{String getBucketLocation()}}, which is used for DDB binding,
We can also use this to determine the s3 endpoint, to avoid recurrent issues with auth failures
related to it not being valid
> Still need to handle: buckets on third-party servers, and the inevitability that new
AWS regions will be added after the Hadoop version & AWS Jar is shipped and frozen

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message