You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Thomas Demoor (JIRA)" <ji...@apache.org> on 2014/11/03 16:03:34 UTC
[jira] [Updated] (HADOOP-11261) Set custom endpoint for S3A
[ https://issues.apache.org/jira/browse/HADOOP-11261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Demoor updated HADOOP-11261:
-----------------------------------
Attachment: JIRA-11261.patch
Change proposed by [~tsato] in the comments of [HADOOP-10400|https://issues.apache.org/jira/browse/HADOOP-10400?focusedCommentId=14104967&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14104967].
Additions:
* possible URI malformed exception caught and logged as error
* added a documented test that ran succesfully against buckets in Ireland and Oregon regions
In order to design a meaningful test I had to expose a public getter for the AmazonS3Client in S3AFileSystem :-( To indicate to other developers that manipulating this object can cause errors a "Here be dragons" warning was added as a comment :-) Probably there is a better and standardized way (annotation?) to indicate this in Hadoop... Anyone?
Note: related to [HADOOP-11171|https://issues.apache.org/jira/browse/HADOOP-11171] as the test class is shared. The last one to get accepted will probably need to be diffed vs trunk again.
> Set custom endpoint for S3A
> ---------------------------
>
> Key: HADOOP-11261
> URL: https://issues.apache.org/jira/browse/HADOOP-11261
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Reporter: Thomas Demoor
> Attachments: JIRA-11261.patch
>
>
> Use a config setting to allow customizing the used AWS region.
> It also enables using a custom url pointing to an S3-compatible object store.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)