[
https://issues.apache.org/jira/browse/MESOS-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Hartmann updated MESOS-6294:
------------------------------------
Description:
It is awkward and difficult to support development of a generic custom executor
when TaskInfos may not contain both a CommandInfo and an ExecutorInfo.
A generic CustomExecutor would like to be able to use the CommandInfo of a
TaskInfo in the launchTask call to determine what action to take. The mutual
exclusion of those two elements of a TaskInfo is not a good way to indicate a
desire to use the CmdExecutor or a CustomExecutor.
was:
It is awkward and difficult to support development of a generic custom executor
when TaskInfos may not contain both a CommandInfo and an ExecutorInfo.
A generic CustomExecutor would like to be able to use the CommandInfo of a
TaskInfo in the launchTask call to determine what action to take. The mutual
exclusion of those to elements of a TaskInfo is not a good way to indicate a
desire to use the CmdExecutor or a CustomExecutor.
> TaskInfo should allow CommandInfo and ExecutorInfo
> --------------------------------------------------
>
> Key: MESOS-6294
> URL: https://issues.apache.org/jira/browse/MESOS-6294
> Project: Mesos
> Issue Type: Improvement
> Reporter: Gabriel Hartmann
>
> It is awkward and difficult to support development of a generic custom
> executor when TaskInfos may not contain both a CommandInfo and an
> ExecutorInfo.
> A generic CustomExecutor would like to be able to use the CommandInfo of a
> TaskInfo in the launchTask call to determine what action to take. The mutual
> exclusion of those two elements of a TaskInfo is not a good way to indicate a
> desire to use the CmdExecutor or a CustomExecutor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
