[
https://issues.apache.org/jira/browse/HADOOP-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15805774#comment-15805774
]
Steve Loughran edited comment on HADOOP-13336 at 1/6/17 9:16 PM:
-----------------------------------------------------------------
"fs.s3a.impl". is the only property you can't stamp on. I'll extend the test to
make sure that the metadatatore one survivces
{{value==null}}.
I don't think so either, but some of the underlying code hinted at it. I'll cut
it, as it shouldn't happen.
thanks for the feedback; I'll do an iteration on it.
regarding the log4.properties, I had left that out the stuff I was checking in,
but had got my git diff wrong. Sorry.
was (Author: [email protected]):
h2. "fs.s3a.impl". is the only property you can't stamp on. I'll extend the
test to make sure that the metadatatore one survivces
h2. {{value==null}}.
I don't think so either, but some of the underlying code hinted at it. I'll cut
it, as it shouldn't happen.
thanks for the feedback; I'll do an iteration on it.
regarding the log4.properties, I had left that out the stuff I was checking in,
but had got my git diff wrong. Sorry.
> 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
> Assignee: Steve Loughran
> Attachments: HADOOP-13336-HADOOP-13345-001.patch,
> HADOOP-13336-HADOOP-13345-002.patch, HADOOP-13336-HADOOP-13345-003.patch
>
>
> 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]
