You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Sean Mackrory (JIRA)" <ji...@apache.org> on 2017/01/26 16:48:24 UTC
[jira] [Created] (HADOOP-14027) Implicitly creating DynamoDB table
ignores endpoint config
Sean Mackrory created HADOOP-14027:
--------------------------------------
Summary: 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
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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org