[
https://issues.apache.org/jira/browse/HADOOP-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417101#comment-15417101
]
Steve Loughran commented on HADOOP-13336:
-----------------------------------------
There's another config strategy, where we configure an endpoint and then assign
buckets to them by way of domains
{code}
fs.s3a.endpoint.eu.address=frankfurt.s3.aws.com
fs.s3a.endpoint.eu.awsid=AWSID
fs.s3a.endpoint.eu.secret=AWSSECRET
{code}
Then you'd refer to a bucket by bucket.endpoint: {{s3a://stevel.frankfurt}}
This is how openstack is configured. Where it might cause problems is for
s3-compatible installations in use today, where an FQDN is used
> support cross-region operations in S3a
> --------------------------------------
>
> Key: HADOOP-13336
> URL: https://issues.apache.org/jira/browse/HADOOP-13336
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
> Priority: Minor
>
> S3a now supports different regions, by way of declaring the endpoint —but you
> can't do things like read in one region, write back in another (e.g. a distcp
> backup), because only one region can be specified in a configuration.
> If s3a supported region declaration in the URL, e.g. s3a://b1.frankfurt
> s3a://b2.seol , then this would be possible.
> Swift does this with a full filesystem binding/config: endpoints, username,
> etc, in the XML file. Would we need to do that much? It'd be simpler
> initially to use a domain suffix of a URL to set the region of a bucket from
> the domain and have the aws library sort the details out itself, maybe with
> some config options for working with non-AWS infra
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
