[
https://issues.apache.org/jira/browse/HDFS-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802944#comment-13802944
]
Hudson commented on HDFS-5403:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #4649 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/4649/])
HDFS-5403. WebHdfs client cannot communicate with older WebHdfs servers post
HDFS-5306. Contributed by Aaron T. Myers. (atm:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1535056)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/web/JsonUtil.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/web/TestJsonUtil.java
> 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-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)
