[
https://issues.apache.org/jira/browse/SPARK-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050804#comment-14050804
]
Martin Zapletal commented on SPARK-1614:
----------------------------------------
I am considering moving the protobufs to a new object - something like object
org.apache.spark.MesosTaskState. Is that acceptable solution with regards to
the requirements (to avoid the conflicts)? If not, can you please suggest which
place would be the best for it?
> Move Mesos protobufs out of TaskState
> -------------------------------------
>
> Key: SPARK-1614
> URL: https://issues.apache.org/jira/browse/SPARK-1614
> Project: Spark
> Issue Type: Bug
> Components: Mesos
> Affects Versions: 0.9.1
> Reporter: Shivaram Venkataraman
> Priority: Minor
> Labels: Starter
>
> To isolate usage of Mesos protobufs it would be good to move them out of
> TaskState into either a new class (MesosUtils ?) or
> CoarseGrainedMesos{Executor, Backend}.
> This would allow applications to build Spark to run without including
> protobuf from Mesos in their shaded jars. This is one way to avoid protobuf
> conflicts between Mesos and Hadoop
> (https://issues.apache.org/jira/browse/MESOS-1203)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
