Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 6 Jan 2017 21:42:58 +0000 (UTC)
From: "Aaron Fabbri (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12986154.1467375251000.670599.1483738978497@Atlassian.JIRA>
In-Reply-To: <JIRA.12986154.1467375251000@Atlassian.JIRA>
References: <JIRA.12986154.1467375251000@Atlassian.JIRA> <JIRA.12986154.1467375251571@arcas>
Subject: [jira] [Commented] (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: Fri, 06 Jan 2017 21:43:00 -0000


    [ https://issues.apache.org/jira/browse/HADOOP-13336?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15=
805850#comment-15805850 ]=20

Aaron Fabbri commented on HADOOP-13336:
---------------------------------------

+1 (binding only on HADOOP-13345 feature branch).

Excited about this feature.  Also happy the implementation turned out to be=
 pretty simple.

> 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-HA=
DOOP-13345-002.patch, HADOOP-13336-HADOOP-13345-003.patch, HADOOP-13336-HAD=
OOP-13345-004.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