[HADOOP-16393] S3Guard init command uses global settings, not those of target bucket

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 3.2.0
• Component/s: fs/s3
• Target Version/s: 3.4.0
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 25/Jun/19 16:17
• Updated: 27/Feb/21 10:56
• Resolved: 27/Feb/21 10:56

Description

If you call s3guard init s3a://name/ then the custom bucket options of fs.s3a.bucket.name are not picked up, instead the global value is used.

Fix: take the name of the bucket and use that to eval properties and patch the config used for the init command.

Issue Links

• causes: HADOOP-16436 Fix ITestS3GuardToolLocal#testInitNegativeRead test failure
• links to: GitHub Pull Request #1012