Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
Description
Currently, we use protobuf reflection APIs to (de)serialize to/from JSON. This means a lot of custom code. There are places where we forgot to customize (e.g. for Map, MESOS-9901). Also, there is a performance regression in protobuf reflection if we upgrade our protobuf library to 3.7.x (see MESOS-9896 and related tickets).
Thus it would beneficial to make use of the built-in json utilises to do the mapping.
Attachments
Issue Links
- duplicates
-
MESOS-9896 Consider using protobuf provided json conversion facilities rather than custom ones.
- Accepted