You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Brahma Reddy Battula (Jira)" <ji...@apache.org> on 2020/04/10 18:15:05 UTC
[jira] [Updated] (HADOOP-16362)
ITestS3GuardToolDynamoDB.testDynamoDBInitDestroyCycle fails if test bucket
isn't on demand
[ https://issues.apache.org/jira/browse/HADOOP-16362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brahma Reddy Battula updated HADOOP-16362:
------------------------------------------
Target Version/s: 3.4.0 (was: 3.3.0)
Bulk update: moved all 3.3.0 non-blocker issues, please move back if it is a blocker.
> ITestS3GuardToolDynamoDB.testDynamoDBInitDestroyCycle fails if test bucket isn't on demand
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-16362
> URL: https://issues.apache.org/jira/browse/HADOOP-16362
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> After HADOOP-15563, if the default s3guard bucket for an FS isn't on-demand, then {{ITestS3GuardToolDynamoDB.testDynamoDBInitDestroyCycle}} fails.
> This is because it creates an on-demand DDB table using a dynamodb// ref, but then calls set-capacity on the original FS URL -which then uses any existing table if it is present. And if that table is provisioned, the set capacity call succeeds.
> Fix: the set-capacity call to take the dynamodb:// URL too
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org