[
https://issues.apache.org/jira/browse/HADOOP-14027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mingliang Liu updated HADOOP-14027:
-----------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: HADOOP-13345
Status: Resolved (was: Patch Available)
Committed to feature branch. Thanks for your contribution [~mackrorysd]. Thanks
for your review, [~fabbri].
> 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
> Fix For: HADOOP-13345
>
> Attachments: HADOOP-14027-HADOOP-13345.001.patch,
> HADOOP-14027-HADOOP-13345.002.patch
>
>
> 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]
