[
https://issues.apache.org/jira/browse/HADOOP-10511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974535#comment-13974535
]
Daniel Darabos commented on HADOOP-10511:
-----------------------------------------
Looks like maybe you need to specify the fully qualified class name:
$ cd hadoop-common/hadoop-common-project
$ mvn
-Dtest=org.apache.hadoop.fs.s3native.TestInMemoryNativeS3FileSystemContract#testListStatusWithPassword
test
With this I get:
Failed tests:
TestInMemoryNativeS3FileSystemContract>NativeS3FileSystemContractBaseTest.testListStatusWithPassword:81
expected:<s3n://key:pass/[email protected]/test> but was:<s3n://key:pass/test>
Thanks for the pointer to the wiki! I'll upload a --no-prefix patch.
> s3n:// incorrectly handles URLs with secret keys that contain a slash
> ---------------------------------------------------------------------
>
> Key: HADOOP-10511
> URL: https://issues.apache.org/jira/browse/HADOOP-10511
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Reporter: Daniel Darabos
> Attachments: HADOOP-10511.patch
>
>
> This is similar to HADOOP-3733, but happens on s3n:// instead of s3://.
> Essentially if I have a path like "s3n://key:pass%[email protected]/test",
> it will under certain circumstances be replaced with "s3n://key:pass/test"
> which then causes "Invalid hostname in URI" exceptions.
> I have a unit test and a fix for this. I'll make a pull request in a moment.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
