[
https://issues.apache.org/jira/browse/HADOOP-13589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818945#comment-15818945
]
Chris Nauroth commented on HADOOP-13589:
----------------------------------------
Reviewing patch 004, we still need to update {{NullMetadataStore#toString}} to
avoid the unnecessary {{StringBuilder}}. Also, some of the contract subclasses
are now instantiating their own {{Configuration}} while others are calling
{{super.createConfiguration()}} and then overriding specific properties. I
think the latter is better so that these suites would inherit changes in the
configuration logic from the base class.
This definitely works though for running the contract tests with S3Guard
enabled and integrated with DynamoDB. I did a test run both with and without
the new profiles.
> S3Guard: Allow execution of all S3A integration tests with S3Guard enabled.
> ---------------------------------------------------------------------------
>
> Key: HADOOP-13589
> URL: https://issues.apache.org/jira/browse/HADOOP-13589
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: HADOOP-13345
> Reporter: Chris Nauroth
> Assignee: Steve Loughran
> Attachments: HADOOP-13589-HADOOP-13345-001.patch,
> HADOOP-13589-HADOOP-13345-002.patch, HADOOP-13589-HADOOP-13345-002.patch,
> HADOOP-13589-HADOOP-13345-004.patch
>
>
> With S3Guard enabled, S3A must continue to be functionally correct. The best
> way to verify this is to execute our existing S3A integration tests in a mode
> with S3A enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
