[
https://issues.apache.org/jira/browse/HDFS-7816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336890#comment-14336890
]
Haohui Mai commented on HDFS-7816:
----------------------------------
bq. maintaining compatibility takes precedence over being standard compliant,
because things stop working and business are impacted.
IMO this is a bug of implementing the spec instead of a feature. One thing to
note is that the scope of the compatibility of WebHDFS is much larger. There
are many other investments that rely on the fact that the WebHDFS server is
compliant with RFC 3986. Just take a few examples:
* Microsoft .NET SDK For Hadoop
(http://hadoopsdk.codeplex.com/wikipage?title=WebHDFS%20Client)
* Python (https://pypi.python.org/pypi/WebHDFS/0.2.0)
* Proxy-based solutions, like Knox and HttpFS
* Reverse proxy standing in front of WebHDFS
This bug prevents all of the above libraries working properly. I think that in
this case we also need to consider the use cases of the above libraries as well.
> Unable to open webhdfs paths with "+"
> -------------------------------------
>
> Key: HDFS-7816
> URL: https://issues.apache.org/jira/browse/HDFS-7816
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Affects Versions: 2.7.0
> Reporter: Jason Lowe
> Assignee: Kihwal Lee
> Priority: Blocker
> Attachments: HDFS-7816.patch, HDFS-7816.patch
>
>
> webhdfs requests to open files with % characters in the filename fail because
> the filename is not being decoded properly. For example:
> $ hadoop fs -cat 'webhdfs://nn/user/somebody/abc%def'
> cat: File does not exist: /user/somebody/abc%25def
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
