hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5403) WebHdfs client cannot communicate with older WebHdfs servers post HDFS-5306
Date Wed, 23 Oct 2013 00:22:42 GMT

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

Aaron T. Myers commented on HDFS-5403:
--------------------------------------

While I agree in principle, would you mind if we did that in a separate JIRA? I'd really like
to keep this fix small and isolated. If that's amenable to you, I'll go ahead and file another
one.

> WebHdfs client cannot communicate with older WebHdfs servers post HDFS-5306
> ---------------------------------------------------------------------------
>
>                 Key: HDFS-5403
>                 URL: https://issues.apache.org/jira/browse/HDFS-5403
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>    Affects Versions: 2.2.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>         Attachments: HDFS-5403.patch
>
>
> HDFS-5306 introduced the field infoSecurePort to the DatanodeIDProto PB definition and
made it optional for compatibility purposes. However, we don't correctly the handle the case
when this field is not present when deserializing the response from a WebHdfs request. This
results in an NPE at the client when this occurs.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message