[
https://issues.apache.org/jira/browse/HADOOP-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory resolved HADOOP-14023.
------------------------------------
Resolution: Resolved
Yes this is fixed. The root of the problem was an imperfect way of translating
from endpoint to region, and there is now no codepath where the region isn't
determined by bucket or by configuration directly.
> S3Guard: DynamoDBMetadataStore logs nonsense region
> ---------------------------------------------------
>
> Key: HADOOP-14023
> URL: https://issues.apache.org/jira/browse/HADOOP-14023
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: HADOOP-13345
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Priority: Minor
> Attachments: HADOOP-14023-HADOOP-13345.001.patch
>
>
> When you specify a DynamoDB endpoint instead of it using the same one as the
> S3 bucket, it thinks the region is "dynamodb":
> {code}
> > bin/hadoop s3a init -m dynamodb://region-test
> 2017-01-25 11:41:28,006 INFO s3guard.S3GuardTool: create metadata store:
> dynamodb://region-test scheme: dynamodb
> 2017-01-25 11:41:28,116 WARN util.NativeCodeLoader: Unable to load
> native-hadoop library for your platform... using builtin-java classes where
> applicable
> 2017-01-25 11:41:29,421 INFO s3guard.DynamoDBMetadataStore: Creating
> non-existent DynamoDB table region-test in region dynamodb
> 2017-01-25 11:41:34,637 INFO s3guard.S3GuardTool: Metadata store
> DynamoDBMetadataStore{region=dynamodb, tableName=region-test} is initialized.
> {code}
> My guess is it's because of DynamoDBMetadataStore.initialize will call
> getEndpointPrefix, and all the published endpoints for DynamoDB actually
> start with dynamodb.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
