Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 11 Jan 2017 14:30:59 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12986154.1467375251000.709388.1484145059096@Atlassian.JIRA>
In-Reply-To: <JIRA.12986154.1467375251000@Atlassian.JIRA>
References: <JIRA.12986154.1467375251000@Atlassian.JIRA> <JIRA.12986154.1467375251571@arcas>
Subject: [jira] [Updated] (HADOOP-13336) S3A to support per-bucket
 configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 11 Jan 2017 14:31:01 -0000


     [ https://issues.apache.org/jira/browse/HADOOP-13336?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated HADOOP-13336:
------------------------------------
    Attachment: HADOOP-13336-011.patch

Turns out that the patch doesn't work in branch-2.8, as HADOOP_SECURITY_CRE=
DENTIAL_PROVIDER_PATH isn't in CommonConfigurationKeysPublic.

Patch 011 inlines the property to S3AUtils, makes package private for testi=
ng. Although it's only needed for Branch-2.8, I'm going to apply it everywh=
ere for consistency

> 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-006.patch, HADOOP-13336-007.patch, HADO=
OP-13336-010.patch, HADOOP-13336-011.patch, HADOOP-13336-HADOOP-13345-001.p=
atch, HADOOP-13336-HADOOP-13345-002.patch, HADOOP-13336-HADOOP-13345-003.pa=
tch, HADOOP-13336-HADOOP-13345-004.patch, HADOOP-13336-HADOOP-13345-005.pat=
ch, HADOOP-13336-HADOOP-13345-006.patch, HADOOP-13336-HADOOP-13345-008.patc=
h, HADOOP-13336-HADOOP-13345-009.patch, HADOOP-13336-HADOOP-13345-010.patch
>
>
> S3a now supports different regions, by way of declaring the endpoint =E2=
=80=94but you can't do things like read in one region, write back in anothe=
r (e.g. a distcp backup), because only one region can be specified in a con=
figuration.
> If s3a supported region declaration in the URL, e.g. s3a://b1.frankfurt s=
3a://b2.seol , then this would be possible.=20
> Swift does this with a full filesystem binding/config: endpoints, usernam=
e, etc, in the XML file. Would we need to do that much? It'd be simpler ini=
tially to use a domain suffix of a URL to set the region of a bucket from t=
he 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org