hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Mackrory (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-14027) Implicitly creating DynamoDB table ignores endpoint config
Date Wed, 08 Mar 2017 15:13:38 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-14027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Sean Mackrory updated HADOOP-14027:
    Attachment: HADOOP-14027-HADOOP-13345.002.patch

Attaching a patch incorporating [~liuml07]'s feedback. All S3 tests are running now but I'm
pretty optimistic given the minor nature of the changes...

> 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
>         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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message