You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/01/12 14:44:40 UTC

[jira] [Resolved] (SPARK-1614) Move Mesos protobufs out of TaskState

     [ https://issues.apache.org/jira/browse/SPARK-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen resolved SPARK-1614.
------------------------------
    Resolution: Won't Fix

> 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.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org