[
https://issues.apache.org/jira/browse/HADOOP-13589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-13589:
------------------------------------
Attachment: HADOOP-13589-HADOOP-13345-001.patch
Patch 001
Adds profiles: s3guard, dynamo and non-auth, to enable s3guard, switch from
local to dynamo and from authoritative to non-authoritative. The last two only
do anything useful unless s3guard is enabled.
* if s3guard is set via the test runner properties, s3guard is set up with the
local or dynamo db metastore and auth options, with ddb.create=true set to
create the db.
* testing section in s3guard updated.
Test: s3 ireland, with local and dynamo, auth & non-auth, serial and parallel
test runs.
> 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
> Reporter: Chris Nauroth
> Assignee: Steve Loughran
> Attachments: HADOOP-13589-HADOOP-13345-001.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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
