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

Hadoop QA commented on HADOOP-14448:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m 10s{color} 
| {color:red} HADOOP-14448 does not apply to HADOOP-13345. Rebase required? 
Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. 
{color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-14448 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12871724/HADOOP-14448-HADOOP-13345.001.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/12469/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Play nice with ITestS3AEncryptionSSEC
> -------------------------------------
>
>                 Key: HADOOP-14448
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14448
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: HADOOP-13345
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>         Attachments: HADOOP-14448-HADOOP-13345.001.patch
>
>
> HADOOP-14035 hasn't yet been merged with HADOOP-13345, but it adds tests that 
> will break when run with S3Guard enabled. It expects that certain filesystem 
> actions will throw exceptions when the client-provided encryption key is not 
> configured properly, but those actions may sometimes bypass S3 entirely 
> thanks to S3Guard (for example, getFileStatus may not actually need to invoke 
> s3GetFileStatus). If the exception is never thrown, the test fails.
> At a minimum we should tweak the tests so they definitely invoke S3 directly, 
> or just skip the offending tests when anything but the Null implementation is 
> in use. This also opens the larger question of whether or not S3Guard should 
> be serving up metadata that is otherwise only accessible when an encryption 
> key is provided.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to