[
https://issues.apache.org/jira/browse/MESOS-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652783#comment-16652783
]
Benjamin Mahler commented on MESOS-8309:
----------------------------------------
{noformat}
commit 5b8f632e75d3c20be172c1678c04f77ae18cda1a
Author: Benjamin Mahler <[email protected]>
Date: Tue Oct 16 11:54:25 2018 -0700
Documented that UUID is a 128 bits (or 16 bytes).
This came up when James DeFelice was asking about the number
of bytes in this message. We should document it.
Review: https://reviews.apache.org/r/69053
{noformat}
> Introduce a UUID message type
> -----------------------------
>
> Key: MESOS-8309
> URL: https://issues.apache.org/jira/browse/MESOS-8309
> Project: Mesos
> Issue Type: Task
> Reporter: Jan Schlicht
> Assignee: Jan Schlicht
> Priority: Major
> Labels: mesosphere
> Fix For: 1.5.0
>
>
> Currently when UUID need to be part of a protobuf message, we use a byte
> array field for that. This has some drawbacks, especially when it comes to
> outputting the UUID in logs: To stringify the UUID field, we first have to
> create a stout UUID, then call {{.toString()}} of that one. It would help to
> have a UUID type in {{mesos.proto}} and provide a stringification function
> for it in {{type_utils.hpp}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
