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 "Steve Loughran (Jira)" <ji...@apache.org> on 2019/10/02 17:53:00 UTC
[jira] [Commented] (HADOOP-16393) S3Guard init command uses global
settings, not those of target bucket
[ https://issues.apache.org/jira/browse/HADOOP-16393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943040#comment-16943040 ]
Steve Loughran commented on HADOOP-16393:
-----------------------------------------
The issue here is that we need to pick up the table name if not set; If I do that on the CLI all is good.
{code:java}
bin/hadoop s3guard -D fs.s3a.s3guard.ddb.table=hwdev-steve-ireland-new init s3a://hwdev-steve-ireland-new/
{code}
> S3Guard init command uses global settings, not those of target bucket
> ---------------------------------------------------------------------
>
> Key: HADOOP-16393
> URL: https://issues.apache.org/jira/browse/HADOOP-16393
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.2.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Fix For: 3.3.0
>
>
> If you call {{s3guard init s3a://name/}} then the custom bucket options of fs.s3a.bucket.name are not picked up, instead the global value is used.
> Fix: take the name of the bucket and use that to eval properties and patch the config used for the init command.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org