[
https://issues.apache.org/jira/browse/HADOOP-14090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated HADOOP-14090:
-----------------------------------
Attachment: HADOOP-14090-HADOOP-13345.001.patch
Attaching a first stab that I think basically works. Most existing tests pass
and I think the only failures are unrelated. I still need to look into a few
assumptions (like if there's ever a reason why you would / could specify both
the region and an endpoint) and do more testing (not sure if region is
something that can be tested well outside of just running tests with various
values for that property in the test config - I suspect not).
For the CLI tool, to specify a region instead of an endpoint (-e), -r is
already used for specifying read throughput on the init command. So I renamed
everything to full words. Single letters is just going to get crazier. I'm
about to do some more work on the prune command where I'm considering bigger
changes to the way all these options get specified, so we'll see.
The other thing is that the S3 bucket's region was getting looked up in a
couple of different places, so similarly this config is getting looked up in a
few different layers. Might be good to reconsider that structure, but perhaps
that's best done as a separate issue....
> 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
