[HADOOP-15845] s3guard init and destroy command will create/destroy tables if ddb.table & region are set

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.1
• Component/s: fs/s3
• Release Note: `hadoop s3guard destroy` and `hadoop s3guard init` now require a MetadataStore URI or a S3A URI to be explicitly provided on the command-line to perform the action.
• Assignee: Gabor Bota
• Reporter: Steve Loughran
• Created: 11/Oct/18 15:37
• Updated: 11/Dec/18 16:06
• Resolved: 11/Dec/18 15:34

Description

If you have s3guard set up with a table name and a region, then s3guard init will automatically create the table, without you specifying a bucket or URI.

I had expected the command just to print out its arguments, but it actually did the init with the default bucket values

Even worse, `hadoop s3guard destroy` will destroy the table.

This is too dangerous to allow. The command must require either the name of a bucket or an an explicit ddb table URI

Issue Links

• is related to: HADOOP-14109 improvements to S3GuardTool destroy command
• is related to: HADOOP-14927 ITestS3GuardTool failures in testDestroyNoBucket()