hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Mackrory (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-14023) S3Guard:
Date Wed, 25 Jan 2017 18:47:26 GMT
Sean Mackrory created HADOOP-14023:

             Summary: S3Guard: 
                 Key: HADOOP-14023
                 URL: https://issues.apache.org/jira/browse/HADOOP-14023
             Project: Hadoop Common
          Issue Type: Bug
            Reporter: Sean Mackrory

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.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message