You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2018/02/19 17:31:00 UTC
[jira] [Resolved] (HADOOP-15201) Automatically determine region &
hence S3 endpoint of buckets
[ 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 it
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org