Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-5408

Optional fields in PB definitions should be optional in HTTP deserialization as well

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 2.2.0
    • Fix Version/s: None
    • Component/s: webhdfs
    • Labels:
      None
    • Target Version/s:

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              atm Aaron Myers

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment