You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Gabor Bota (JIRA)" <ji...@apache.org> on 2018/12/05 14:47:00 UTC
[jira] [Issue Comment Deleted] (HADOOP-15845) s3guard init and
destroy command will create/destroy tables if ddb.table & region are set
[ https://issues.apache.org/jira/browse/HADOOP-15845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Bota updated HADOOP-15845:
--------------------------------
Comment: was deleted
(was: I think that bucket in cli should be mandatory to these commands. This would make more sense after the HADOOP-14927 fix. I'll upload a patch for it soon with tests.)
> 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
>
> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org