[HADOOP-14109] improvements to S3GuardTool destroy command

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 3.1.0
• Component/s: fs/s3
• Assignee: Unassigned
• Reporter: Steve Loughran
• Created: 23/Feb/17 11:42
• Updated: 27/Feb/21 11:12
• Resolved: 27/Feb/21 11:12

Description

The S3GuardTool destroy operation initializes dynamoDB, and in doing so has some issues

1. if the version of the table is incompatible, init fails, so table isn't deleteable
2. if the system is configured to create the table on demand, then whenever destroy is called for a table that doesn't exist, it gets created and then destroyed.

Issue Links

• is related to: HADOOP-15428 s3guard bucket-info will create s3guard table if FS is set to do this automatically
• relates to: HADOOP-15845 s3guard init and destroy command will create/destroy tables if ddb.table & region are set