[
https://issues.apache.org/jira/browse/HADOOP-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15749088#comment-15749088
]
Steve Loughran commented on HADOOP-13336:
-----------------------------------------
thanks for this
I was wondering until that last sentence why you were proposing something
bucket-last (little endian?) until you got to that bit about names containing
the "." character.
I'm not actually sure that Hadoop copes with "." in a name; certainly S3A
assume that it's the host: {{bucket = name.getHost();}}, and as that's the
bucket name used in generating upload requests, you won't be able to PUT any
data in them. Nobody has ever complained to us about that _yet_.
What about from a "fielding support calls" perspective? I think we'd need a way
to get a list of all config options which have been picked up by a bucket,
otherwise a single typo would result in the default value being picked up
instead.
> S3A to support per-bucket configuration
> ---------------------------------------
>
> 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
>
> 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]
