[
https://issues.apache.org/jira/browse/HADOOP-14305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982717#comment-15982717
]
Steve Loughran commented on HADOOP-14305:
-----------------------------------------
ooh, I think you went to more effort than was needed for that branch-2 patch;
the {{intercept()}} call works on b2, it just needs to take a
{{Callable<Void>}}. I'll just take the trunk patch and do that tweak.
Also, and I'm not going to change it, your intercept lambdas don't need to
raise an exception the clause didn't raise the exception you wanted. Intercept
generates its own exception, the latest versions (in s3guard) including the
response of the clause
Example:
{code}
intercept(IOException.class, "", () -> {{ return File.getStatus(new Path(new
URI("s3a://bucket/no-such-path"); })
{code}
This will raise an assertion saying something like {{"Expected an IOException,
got FileStatus("s3a://bucket/no-such-path", ..."}}. It's aim is to provide as
much useful diagnostics automatically
> S3A SSE tests won't run in parallel: Bad request in directory GetFileStatus
> ---------------------------------------------------------------------------
>
> Key: HADOOP-14305
> URL: https://issues.apache.org/jira/browse/HADOOP-14305
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 2.9.0
> Reporter: Steve Loughran
> Assignee: Steve Moist
> Priority: Minor
> Attachments: HADOOP-14305-001.patch, HADOOP-14305-002.patch,
> HADOOP-14305-branch-2-002.patch
>
>
> The S3a encryption tests all run in parallel (they were interfering with each
> other, apparently). This adds ~1 min to the test runs.
> They should run in serial. That they fail when this is attempted due to Bad
> Auth problems must be considered a serious problem, as is indicates issues
> related to working with SSE encryption from hadoop
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
