[
https://issues.apache.org/jira/browse/HADOOP-14090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870984#comment-15870984
]
Aaron Fabbri commented on HADOOP-14090:
---------------------------------------
Some quick comments before doing a more in-depth review:
- Now is good time to clean up CLI arguments, since compatibility will be a
concern post-merge. I'm fine with some of that landing in this patch.
- Region and endpoint are mutually exclusive from everything I've read (e.g.
[dev
guide|http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/java-dg-region-selection.html]).
Region is short-hand for endpoint. We should specify behavior if both are
specified: Log an error and ignore region (use endpoint) if both configuration
parameters are set.
- We should also streamline the init and config code so these things are set up
in one place (e.g. the region lookup you mention).
> 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
