[
https://issues.apache.org/jira/browse/HDFS-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802407#comment-13802407
]
Andrew Wang commented on HDFS-5403:
-----------------------------------
This change looks good, thanks Aaron. What do you think about doing the same
treatment for other optional fields in DatanodeInfoProto, e.g. {{capacity}},
{{dfsUsed}}, etc? Right now I know we set them to dummy values on the NN so
this doesn't come up, but we really should try to make our JSON parsing
consistent with our PB defs.
> 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)
