[ 
https://issues.apache.org/jira/browse/HADOOP-15845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717444#comment-16717444
 ] 

Hudson commented on HADOOP-15845:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15589 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/15589/])
HADOOP-15845. Require explicit URI on CLI for s3guard init and destroy. 
(mackrorysd: rev 1a25bbe9ec7155712a82b157a8379826f8c79d4b)
* (edit) 
hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/s3guard/ITestS3GuardToolDynamoDB.java
* (edit) 
hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/s3guard/AbstractS3GuardToolTestBase.java
* (edit) 
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/s3guard/S3GuardTool.java


> s3guard init and destroy command will create/destroy tables if ddb.table & 
> region are set
> -----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-15845
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15845
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.1.1
>            Reporter: Steve Loughran
>            Assignee: Gabor Bota
>            Priority: Major
>         Attachments: HADOOP-15845.001.patch
>
>
> 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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to