[
https://issues.apache.org/jira/browse/HADOOP-14129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated HADOOP-14129:
-----------------------------------
Attachment: HADOOP-14129-HADOOP-13345.001.patch
Attaching a patch that does just that. I've tested both with and without this
fix, both with and without S3Guard (DynamoDB), and in both US West 2 and
Frankfurt. Frustratingly, every single test passed - couldn't reproduce the
failure. But if this isn't *supposed* to work, probably not too bad to just
push it in and deal with it if it fails again later.
> ITestS3ACredentialsInURL sometimes fails
> ----------------------------------------
>
> Key: HADOOP-14129
> URL: https://issues.apache.org/jira/browse/HADOOP-14129
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: HADOOP-13345
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Attachments: HADOOP-14129-HADOOP-13345.001.patch
>
>
> This test sometimes fails. I believe it's expected that DynamoDB doesn't have
> access to the credentials if they're embedded in the URL instead of the
> configuration (and IMO that's fine - since the functionality hasn't been in
> previous releases and since we want to discourage this practice especially
> now that there are better alternatives). Weirdly, I only sometimes get this
> failure on the HADOOP-13345 branch. But if the problem turns out to be what I
> think it is, a simple Assume should fix it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
