[
https://issues.apache.org/jira/browse/HADOOP-14027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897834#comment-15897834
]
Sean Mackrory commented on HADOOP-14027:
----------------------------------------
This is still a problem and I'm testing a patch for it now. Basically there are
2 options for initialize: one will use the bucket's region regardless, and one
will use the config. If you happen to go through the first,
fs.s3a.s3guard.ddb.region will have no effect - it should override the bucket's
region in that case.
> Implicitly creating DynamoDB table ignores endpoint config
> ----------------------------------------------------------
>
> Key: HADOOP-14027
> URL: https://issues.apache.org/jira/browse/HADOOP-14027
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
>
> When you're using the 'bin/hadoop s3a init' command, it correctly uses the
> endpoint provided on the command-line (if provided), it will then use the
> endpoint in the config (if provided), and failing that it will default to the
> same region as the bucket.
> However if you just set fs.s3a.s3guard.ddb.table.create to true and create a
> directory for a new bucket / table, it will always use the same region as the
> bucket, even if another endpoint is configured.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
