[MESOS-9901] jsonify uses non-standard mapping for protobuf map fields.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.9.0
• Component/s: json api
• Labels: foundations
• Target Version/s: 1.9.0
• Sprint: Resource Mgmt: RI-16 51
• Story Points: 3
• Assignee: Meng Zhu
• Reporter: Meng Zhu
• Created: 23/Jul/19 01:57
• Updated: 31/Jul/19 03:30
• Resolved: 31/Jul/19 03:30

Description

Jsonify current treats protobuf as a regular repeated field. For example, for the schema

message QuotaConfig {
  required string role = 1;

  map<string, Value.Scalar> guarantees = 2;
  map<string, Value.Scalar> limits = 3;
}

it will produce:

{
  "configs": [
    {
      "role": "role1",
      "guarantees": [
        {
          "key": "cpus",
          "value": {
            "value": 1
          }
        },
        {
          "key": "mem",
          "value": {
            "value": 512
          }
        }
      ]
    }
  ]
}

This output cannot be parsed back to proto messages. We need to specialize jsonify for Maps type to get the standard output:

    {
      "configs": [
        {
          "role": "role1",
          "guarantees": {
            "cpus": 1,
            "mem": 512
          }
        }
      ]
    }

Issue Links

• relates to: MESOS-9896 Consider using protobuf provided json conversion facilities rather than custom ones.