[
https://issues.apache.org/jira/browse/HADOOP-14102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879440#comment-15879440
]
Hudson commented on HADOOP-14102:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11289 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11289/])
HADOOP-14102. Relax error message assertion in S3A test (liuml07: rev
0013090fb4340eadf147054e65a73de20a62c1c1)
* (edit)
hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/ITestS3AEncryptionSSEC.java
> Relax error message assertion in S3A test ITestS3AEncryptionSSEC
> ----------------------------------------------------------------
>
> Key: HADOOP-14102
> URL: https://issues.apache.org/jira/browse/HADOOP-14102
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Mingliang Liu
> Assignee: Mingliang Liu
> Priority: Minor
> Fix For: 2.9.0, 3.0.0-alpha3
>
> Attachments: HADOOP-14102.000.patch
>
>
> [HADOOP-13075] added support for SSE-KMS and SSE-C in s3a filesystem, along
> with integration test
> {{ITestS3AEncryptionSSEC::testCreateFileAndReadWithDifferentEncryptionKey}}.
> For {{AccessDeniedException}} test case, it assumes the error message
> contains string _Forbidden (Service: Amazon S3; Status Code: 403;_, which is
> true in the current AWS java sdk and current S3AFileSystem code path.
> When enabling S3Guard (see feature JIRA [HADOOP-13345]), the code path that
> fails in {{S3AFileSystem}} changes for that test. Specifically, the request
> w/o S3Guard was calling {{getFileStatus()}} and fails with access denied
> exception containing _Forbidden_ keyword; while the request w/ S3Guard is
> able to call {{getFileStatus()}} successfully and then fails later for read
> operations with access denied exception containing _Access Denied_ keyword.
> AWS sdk does not provide the exactly same error message for different
> AccessDeniedExceptions. In the meantime, the AWS sdk may evolve (as we have
> been upgrading the sdk version recently in a timely manner) and the error
> message may be different in the future. This is to relax exception message
> assertion in test.
> Thanks [~fabbri] for discussion. See [HADOOP-13345].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]