[MESOS-3449] Expand the range of integer precision in json <-> protobuf conversions to include unsigned integers

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 0.25.0
• Component/s: stout
• Labels: json mesosphere protobuf
• Story Points: 5
• Assignee: Unassigned
• Reporter: Joseph Wu
• Shepherd: Joris Van Remoortere
• Created: 16/Sep/15 22:05
• Updated: 26/Nov/19 21:09

Description

The previous changes (MESOS-3345) to support integer precision when converting JSON <-> Protobuf did not support precision for unsigned integers between INT64_MAX and UINT64_MAX. (There's some loss, but the conversion is still as good/bad as it was with doubles.)

This problem is due to a limitation in the JSON parsing library we use (PicoJSON), which parses integers as int64_t.

Some possible solutions or things to investigate:

• We can patch PicoJSON to parse some large values as uint64_t.
• We can investigate using another parsing library.
• If we want extra precision beyond 64 or 80 bits per double, one possibility is the GMP library. We'd still need to change the parsing library though.

NOTE: The asV1Protobuf copy needs to also be updated.

Issue Links

• is related to: MESOS-3345 Expand the range of integer precision when converting into/out of json.
• relates to: MESOS-9896 Consider using protobuf provided json conversion facilities rather than custom ones.