[
https://issues.apache.org/jira/browse/MESOS-7228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985195#comment-15985195
]
Zhitao Li commented on MESOS-7228:
----------------------------------
[~guoger], all existing `required` fields in Mesos will still be allowed until
we drop the `syntax = proto2` and move to pure proto3 syntax (which would be a
sweeping incompatible change so we won't do it in V1 API).
However, I don't know what enforcement level is provided by various generated
libraries in different languages after this change, and it's possible that
certain invalid input which used to caught by client libraries now got leaked
to the system. I would advise we add more enforcement around input validation
and ensure fields we care are actually set.
Does this answer your question?
> Upgrade Mesos to build with proto3.
> -----------------------------------
>
> Key: MESOS-7228
> URL: https://issues.apache.org/jira/browse/MESOS-7228
> Project: Mesos
> Issue Type: Improvement
> Reporter: Anand Mazumdar
> Assignee: Zhitao Li
> Priority: Critical
>
> We currently build Mesos with protobuf 2.6.1 and bundle it as a dependency.
> We should upgrade it to use v3.2.0 instead. This would help us use arenas to
> improve performance (MESOS-6971) and also help resolve some bugs around the
> Mesos master not able to handle large protobufs (>64mbs in size, MESOS-4210)
> etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
