hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7816) Unable to open webhdfs paths with "+"
Date Sat, 21 Feb 2015 06:31:12 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14330033#comment-14330033

Haohui Mai commented on HDFS-7816:

bq. I don't think we can rely on clients changing the way the URL is encoded, otherwise we
break compatibility with older clients.
I think Kihwal's patch will work even with older clients. My main concern is that we're relying
on QueryStringDecoder#path to give us a raw path so URI can decode it properly

Speaking about compatibility, note that we need to consider the compatibility of other clients
as well. For example, python clients expects WebHDFS server strictly follows URIs encoding
scheme, that is, the URI that are sent over the wire strictly follows RFC 3986. 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.

> 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

View raw message