[
https://issues.apache.org/jira/browse/HDFS-7816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333386#comment-14333386
]
Kihwal Lee commented on HDFS-7816:
----------------------------------
bq. This is well-defined. If the WebHDFS client happens to diverge from it, it
should be considered as a bug instead of a feature that needs to be
backward-compatible.
This is not the first time this problem was discovered and discussed. The
original webhdfs design is flawed, but we cannot ignore the compatibility.
IMO, maintaining compatibility takes precedence over being standard compliant,
because things stop working and business are impacted.
I think we should definitely fix webhdfs to be RFC3986 compliant, but it must
be done in a way that avoids any breakages due to incompatibility. However,
this jira is intended for making things continue to work in the short term, as
such I suggest we open a new jira and continue discussion there.
> 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)
