Details
-
Sub-task
-
Status: Resolved
-
Minor
-
Resolution: Resolved
-
HADOOP-13345
-
None
-
None
-
None
Description
When you specify a DynamoDB endpoint instead of it using the same one as the S3 bucket, it thinks the region is "dynamodb":
> 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.
My guess is it's because of DynamoDBMetadataStore.initialize will call getEndpointPrefix, and all the published endpoints for DynamoDB actually start with dynamodb.