hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Fabbri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13589) S3Guard: Allow execution of all S3A integration tests with S3Guard enabled.
Date Tue, 10 Jan 2017 00:10:58 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813303#comment-15813303
] 

Aaron Fabbri commented on HADOOP-13589:
---------------------------------------

This looks awesome [~stevel@apache.org].  One minor nit:  I'd expect fs.s3a.metadatastore.authoritative
to be false by default.  That should be the "safer" configuration we encourage for initial
production use.  Does that make sense?  As long as the documentation is clear to this effect,
I'm +1 on this.

> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message