Anand Mazumdar created MESOS-6016:
-------------------------------------
Summary: Expose the unversioned Call and Event Scheduler/Executor
Protobufs.
Key: MESOS-6016
URL: https://issues.apache.org/jira/browse/MESOS-6016
Project: Mesos
Issue Type: Task
Reporter: Anand Mazumdar
Currently, we don't expose the un-versioned (v0) {{Call}}/{{Event}}
scheduler/executor protobufs externally to framework authors. This is a bit
disjoint since we already expose the unversioned Mesos protos. The reasoning
for not doing so earlier was that Mesos would use the v0 protobufs as an
alternative to having separate internal protobufs internally.
However, that is not going to work. Eventually, when we introduce a backward
incompatible change in {{v1}} protobufs, we would create new {{v2}} protobufs.
But, we would need to ensure that {{v2}} protobufs can somehow be translated to
{{v0}} without breaking existing users. That's a pretty hard thing to do! In
the interim, to help framework authors migrate their frameworks (they might be
storing old protobufs in ZK/other reliable storage) , we should expose the v0
scheduler/executor protobufs too and create another internal translation layer
for Mesos.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
