[
https://issues.apache.org/jira/browse/HADOOP-14068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated HADOOP-14068:
-----------------------------------
Attachment: HADOOP-14068-HADOOP-13345.002.patch
I think I've addressed everything I was unhappy with in the previous patch:
mainly the hard-coded bucket, etc. The reason the 2 verifyTable* tests were
failing previously for me turned out to be because of that: if you've
configured S3Guard to use a permanent table rather than naming it after the
bucket you're also using for tests, those tests would make assumptions that are
no longer true. So I think it's good that the tests are inheriting more from
the configuration after this change.
> Add integration test version of TestMetadataStore for DynamoDB
> --------------------------------------------------------------
>
> Key: HADOOP-14068
> URL: https://issues.apache.org/jira/browse/HADOOP-14068
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Attachments: HADOOP-14068-HADOOP-13345.001.patch,
> HADOOP-14068-HADOOP-13345.002.patch
>
>
> I tweaked TestDynamoDBMetadataStore to run against the actual Amazon DynamoDB
> service (as opposed to the "local" edition). Several tests failed because of
> minor variations in behavior. I think the differences that are clearly
> possible are enough to warrant extending that class as an ITest (but
> obviously keeping the existing test so 99% of the the coverage remains even
> when not configured for actual DynamoDB usage).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
