[HADOOP-17822] fs.s3a.acl.default not working after S3A Audit feature added

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.2
• Fix Version/s: 3.3.2
• Component/s: fs/s3
• Labels: pull-request-available
• Target Version/s: 3.3.2
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 30/Jul/21 09:58
• Updated: 24/May/23 19:20
• Resolved: 02/Aug/21 14:36

Description

After HADOOP-17511 the fs.s3a.acl.default propperty isn't being passed through to S3 PUT/COPY requests.

The new RequestFactory is being given the acl values from the S3A FS instance, but the factory is being created before the acl settings are loaded from the configuration.

Fix, and ideally, test (if the getXAttr lets us see this now)

Issue Links

• is caused by: HADOOP-17511 Add an Audit plugin point for S3A auditing/context
• is related to: HADOOP-18685 Amazon S3 disabling ACLs on all new buckets
• links to: GitHub Pull Request #3249