[
https://issues.apache.org/jira/browse/MESOS-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854338#comment-15854338
]
haosdent commented on MESOS-5186:
---------------------------------
[~asottileyelp] Thanks a lot for your answer. I test with a python scheduler
with protobuf3 while the Mesos compile with protobuf2. It works for me.
[Feng Xiao|https://github.com/xfxyjwf] mentioned in
https://groups.google.com/forum/#!topic/protobuf/wAqvtPLBsE8
{quote}
Proto2 and proto3 are wire compatible. The same construct in proto2 and proto3
will have the same binary representation. If your proto only uses features
available in both proto2 and proto3, systems built with proto2 should be able
to communicate with systems built with proto3 without any problem (it's also
true vice versa).
{quote}
at https://groups.google.com/forum/#!topic/protobuf/wAqvtPLBsE8
Since 1.2.0 would be cut shortly, how about put off this to 1.3.0 and let's
continue discuss and review it after 1.2.0 released.
> mesos.interface: Allow using protobuf 3.x
> -----------------------------------------
>
> Key: MESOS-5186
> URL: https://issues.apache.org/jira/browse/MESOS-5186
> Project: Mesos
> Issue Type: Improvement
> Components: python api
> Reporter: Myautsai PAN
> Assignee: Yong Tang
> Priority: Minor
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> We're working on integrating TensorFlow(https://www.tensorflow.org) with
> mesos. Both the two require {{protobuf}}. The python package
> {{mesos.interface}} requires {{protobuf>=2.6.1,<3}}, but {{tensorflow}}
> requires {{protobuf>=3.0.0}} . Though protobuf 3.x is not compatible with
> protobuf 2.x, but anyway we modify the {{setup.py}}
> (https://github.com/apache/mesos/blob/66cddaf/src/python/interface/setup.py.in#L29)
> from {{'install_requires': [ 'google-common>=0.0.1', 'protobuf>=2.6.1,<3'
> ],}} to {{'install_requires': [ 'google-common>=0.0.1', 'protobuf>=2.6.1' ],}}
> It works fine. Would you please consider support protobuf 3.x officially in
> the next release? Maybe just remove the {{,<3}} restriction is enough.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
