[HADOOP-14023] S3Guard: DynamoDBMetadataStore logs nonsense region

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Resolved
• Affects Version/s: HADOOP-13345
• Target Version/s: HADOOP-13345
• Assignee: Sean Mackrory
• Reporter: Sean Mackrory
• Created: 25/Jan/17 18:46
• Updated: 06/Mar/17 18:54
• Resolved: 06/Mar/17 18:54

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.