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] [Issue Comment Deleted] (HADOOP-14489) ITestS3GuardConcurrentOps requires explicit DynamoDB table name to be configured
Date Mon, 05 Jun 2017 21:39:04 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-14489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sean Mackrory updated HADOOP-14489:
-----------------------------------
    Comment: was deleted

(was: So this has always succeeded for me because my auth-keys.xml sets a specific table name.
If I don't, it fails for me no matter how it's run. Attaching a patch that fixes it by initializing
the DynamoDB client using the test file system (so it can use the bucket name as the default
table name). Now it passes for me with and without a specific table name.)

> ITestS3GuardConcurrentOps requires explicit DynamoDB table name to be configured
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-14489
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14489
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>
> testConcurrentTableCreations fails with this: {quote}java.lang.IllegalArgumentException:
No DynamoDB table name configured!{quote}
> I don't think that's necessary - should be able to shuffle stuff around and either use
the bucket name by default (like other DynamoDB tests would) or use the table name that's
configured later in the test.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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


Mime
View raw message