[
https://issues.apache.org/jira/browse/HADOOP-16329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847637#comment-16847637
]
Steve Loughran commented on HADOOP-16329:
-----------------------------------------
Only interesting question here is this should have shown up in the HADOOP-16118
test process, unless maybe my test setup was wrong there (i.e. test bucket
wasn't on demand after all)
> "Wrong Billing mode" test failure in ITestS3GuardToolDynamoDB
> -------------------------------------------------------------
>
> Key: HADOOP-16329
> URL: https://issues.apache.org/jira/browse/HADOOP-16329
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Priority: Minor
>
> Test {{ITestS3GuardToolDynamoDB.testDynamoDBInitDestroyCycle}} failing with
> "wrong billing mode"
> the newly inited test table is coming up with capacity (2, 2) when, because
> the original is (0, 0), the test now expects a PAYG table.
> I think this test is going to fail until the SDK is updated and HADOOP-15563
> in, at least when the source table is on demand.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
