[HADOOP-13336] S3A to support per-bucket configuration

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.0
• Fix Version/s: 2.8.0, 3.0.0-alpha2
• Component/s: fs/s3
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 01/Jul/16 12:14
• Updated: 30/Nov/20 11:26
• Resolved: 12/Jan/17 11:30

Description

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

Issue Links

• is cloned by: HADOOP-17401 GCS to support per-bucket configuration
• is depended upon by: HADOOP-13972 ADLS to support per-store configuration
• is depended upon by: SPARK-20153 Support Multiple aws credentials in order to access multiple Hive on S3 table in spark application
• relates to: HADOOP-13876 S3Guard: better support for multi-bucket access
• relates to: HADOOP-14013 S3Guard: fix multi-bucket integration tests