Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.1.1
-
None
-
None
-
`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.
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
Attachments
Attachments
Issue Links
- is related to
-
HADOOP-14109 improvements to S3GuardTool destroy command
- Resolved
-
HADOOP-14927 ITestS3GuardTool failures in testDestroyNoBucket()
- Resolved