[
https://issues.apache.org/jira/browse/HADOOP-13899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-13899:
------------------------------------
Attachment: HADOOP-13899-HADOOP-13345-002.patch
HADOOP-13899
* in destroy(), do nothing if table==null (fixes some failing tests on jenkins)
* in destroy(), assert that the dynamo DB connection exists. That's done after
the table check, so its actually the situation: {{table != null && dynamoDB ==
null}}; I'd consider that a problem.
* downgrade shutdown log. We shouldn't be adding more information to the normal
output logs when things are working.
* a bit more logging at debug
* marked {{createTable()}} as visible for testing.
> tune dynamodb client & tests
> ----------------------------
>
> Key: HADOOP-13899
> URL: https://issues.apache.org/jira/browse/HADOOP-13899
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.0.0-alpha2
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Attachments: HADOOP-13899-HADOOP-13345-001.patch,
> HADOOP-13899-HADOOP-13345-002.patch
>
>
> While setting up clients for testing dynamo DB, make the tweaks to the dynamo
> store and the s3guard code for better use downstream. These are the kind of
> things we need to round off the code for production use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
