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] [Commented] (HADOOP-14090) Allow users to specify region for DynamoDB table instead of endpoint
Date Fri, 17 Feb 2017 15:29:42 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-14090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871985#comment-15871985

Sean Mackrory commented on HADOOP-14090:

{quote}the endpoint specifies the s3 endpoint for authentication. If I specify DDB region,
what does that mean for the s3a bucket? What if they are different...does that just run DDB
somewhere else?{quote}

There are already distinct configs for the s3 and DynamoDB endpoints, btw, so I didn't think
that would be any more confusing. I've done this a lot in testing and had some requests for
that use case in this feature: if users are going to take advantage of HADOOP-13876, etc.
and use a single table for multiple buckets, perhaps one of the buckets occasionally used
will be in a different region. Not a great idea for that to happen all the time for cost /
performance, but there's no reason it shouldn't work. And it's easier for AWS users to specify
a region than an endpoint.

{quote}Unix convention is to use – for long commands, so if an app supports single char
options, you can combine them tar -xvf == tar -x -v -f. So use "--" as the prefix here.{quote}

Sounds good - I think we should only have the long commands because all options so far are
not combinable anyway - they all take parameters.

> Allow users to specify region for DynamoDB table instead of endpoint
> --------------------------------------------------------------------
>                 Key: HADOOP-14090
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14090
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Sean Mackrory
>         Attachments: HADOOP-14090-HADOOP-13345.001.patch
> Assuming the AWS SDK allows this, I think this would be a better way to configure it
for any usage on AWS itself (with endpoint still being an option for AWS-compatible non-AWS
use cases). Unless users actually care about a specific endpoint, this is easier. Perhaps
less important, HADOOP-14023 shows that inferring the region from the endpoint (which granted,
isn't that necessary) doesn't work very well at all.

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