[
https://issues.apache.org/jira/browse/HADOOP-16187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852995#comment-16852995
]
Steve Loughran commented on HADOOP-16187:
-----------------------------------------
It's a config option: if your
# the auth keys XML file declares that the test bucket uses S3guard
# {{S3AFilesystem.initialize()}} therefore starts starts the DDB metastore
# which tries to bind to the new table ID just generated
# and fails as the table isn't there.
Fix: reset per bucket options about metastore and creation. I'll be including
the fix in HADOOP-15563 as its ~stepping into the same test cases
> ITestS3GuardToolDynamoDB test failures
> --------------------------------------
>
> Key: HADOOP-16187
> URL: https://issues.apache.org/jira/browse/HADOOP-16187
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Priority: Major
>
> two tests failiing in ITestS3GuardToolDynamoDB
> * ITestS3GuardToolDynamoDB.testDynamoDBInitDestroyCycle
> * ITestS3GuardToolDynamoDB.testBucketInfoUnguarded
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
