[jira] [Created] (HADOOP-14094) Rethink S3GuardTool options

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
Report Content as Inappropriate

[jira] [Created] (HADOOP-14094) Rethink S3GuardTool options

JIRA jira@apache.org
Sean Mackrory created HADOOP-14094:

             Summary: Rethink S3GuardTool options
                 Key: HADOOP-14094
                 URL: https://issues.apache.org/jira/browse/HADOOP-14094
             Project: Hadoop Common
          Issue Type: Sub-task
            Reporter: Sean Mackrory

I think we need to rework the S3GuardTool options. A couple of problems I've observed in the patches I've done on top of that and seeing other developers trying it out:

* We should probably wrap the current commands in an S3Guard-specific command, since 'init', 'destroy', etc. don't touch the buckets at all.
* Convert to whole-word options, as the single-letter options are already getting overloaded. Some patches I've submitted have added functionality where the obvious flag is already in use (e.g. -r for region, and read throughput, -m for minutes, and metadatastore uri).  I may do this early as part of HADOOP-14090.
* We have some options that must be in the config in some cases, and can be in the command in other cases. But I've seen someone try to specify the table name in the config and leave out the -m option, with no luck. Also, since commands hard-code table auto-creation, you might have configured table auto-creation, try to import to a non-existent table, and it tells you table auto-creation is off.

We need a more consistent policy for how things should get configured that addresses these problems and future-proofs the command a bit more.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]