[
https://issues.apache.org/jira/browse/HADOOP-13589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816416#comment-15816416
]
Mingliang Liu commented on HADOOP-13589:
----------------------------------------
Yes I think it makes sense to enable integration test integration with local
DynamoDB instance for cost and fast debugging. The only concern was that (I'm
not sure) DynamoDBLocal package is not actively maintained for a while (>1
year), e.g. throttling is not supported.
We can achieve this either by launching a DynamoDBLocal process manually and
setting the DDB endpoint in config as {{http://localhost:8000}} for integration
tests, or by launching an in-memory DynamoDBLocal instance via
{{setUpBeforeClass()}} in each integration test (if the MetadataStore is DDB).
The latter can be further configurable so that we can choose between DDB
simulator and genuine AWS service.
> 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
>
>
> 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]
