[
https://issues.apache.org/jira/browse/HADOOP-14777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-14777:
------------------------------------
Attachment: HADOOP-14777-HADOOP-13345-001.patch
Patch 001. Tested: s3a ireland, localdynamo
One more thought: should we change the policy at the top of the testing.md doc
to say
* submitters MUST declare their s3guard settings in test runs (even if not
enabled)
* submitters SHOULD test with: s3guard ddb/localddb as well as no s3guard, &
declare outcomes.
* submitters SHOULD declare any encryption endpoints used
We effectively have 3 explicit configs to test (none, s3guard local, s3guard
"production), as well as those of encryption (none, SSE-S3, SSE-KMS). three
test runs would suffice to explore the configuration-space if each test run
chose a different encryption & test option.
> S3Guard premerge changes: java 7 build & test tuning
> ----------------------------------------------------
>
> Key: HADOOP-14777
> URL: https://issues.apache.org/jira/browse/HADOOP-14777
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: HADOOP-13345
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: HADOOP-14777-HADOOP-13345-001.patch
>
>
> Another set of changes for S3Guard in preparation for merging via HADOOP-13998
> * checkstyle issues
> * Made Java 7 friendly (indeed, tested applied to branch-2 with some POM
> changes & tested there)
> * improve diagnostics on some test failure. This would address HADOOP-14750.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
