[
https://issues.apache.org/jira/browse/HADOOP-14022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897967#comment-15897967
]
Steve Loughran commented on HADOOP-14022:
-----------------------------------------
Simply the aggregate of HADOOP-13287 and HADOOP-3733
# you need to escape these
# you SHOULD NOT stick AWS secrets in URIs, as they get logged in lots of code
which does not consider that Path variables could contain secrets.
Hadoop 2.8 will warn you from doing this; with per-bucket configs the sole
defensible case "cross-account access" has gone. Please don't.
> S3 connections fails if in-URI AWS secret key contains '+' and '/' both
> ------------------------------------------------------------------------
>
> Key: HADOOP-14022
> URL: https://issues.apache.org/jira/browse/HADOOP-14022
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Affects Versions: 2.7.3
> Reporter: pinkencryption
> Priority: Minor
>
> Hi Guys,
> I am opening a bug here. I am pretty sure it was fixed but I believe this is
> still the case.
> Our secret key contains a "/" and "+" both and it seems all the cases fail
> and keep producing the following error :
> IllegalArgumentException: The bucketName parameter must be specified.
> I would like to know if that is still the case.
> Check old issue here : https://issues.apache.org/jira/browse/HADOOP-13287
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
