You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2013/10/25 03:58:02 UTC

[jira] [Resolved] (HDFS-5408) Optional fields in PB definitions should be optional in HTTP deserialization as well

     [ https://issues.apache.org/jira/browse/HDFS-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Wang resolved HDFS-5408.
-------------------------------

    Resolution: Duplicate

Duping this to HDFS-5419, which although on a branch, will be getting merged soon and will fix this issue.

> Optional fields in PB definitions should be optional in HTTP deserialization as well
> ------------------------------------------------------------------------------------
>
>                 Key: HDFS-5408
>                 URL: https://issues.apache.org/jira/browse/HDFS-5408
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>    Affects Versions: 2.2.0
>            Reporter: Aaron T. Myers
>
> As was pointed out by [~andrew.wang] in HDFS-5403, there are a few fields which are marked as optional in PB definitions but then assumed to always exist in the JSON deserialization of the WebHdfs client. We should handle the possibility that these fields will not be present in WebHdfs as well.



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