airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandr Nikitin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-245) Access to task instance from custom Executor
Date Tue, 21 Jun 2016 14:03:58 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341824#comment-15341824
] 

Alexandr Nikitin commented on AIRFLOW-245:
------------------------------------------

[~jlowin] Thank you for the reply. Yes, I have looked at the MesosExecutor. What I don't like
is the dependency on Airflow. I don't want /cannot install Airflow on Mesos slaves. I want
to use native APIs of Mesos/Marathon/etc. Also I don't want to introduce new Operators. E.g.
I can run DockerOperator on local executor, I want to be able to run the same operator on
Mesos via its API.

> Access to task instance from custom Executor
> --------------------------------------------
>
>                 Key: AIRFLOW-245
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-245
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: executor
>            Reporter: Alexandr Nikitin
>
> I'm writing a custom executor that executes tasks on mesos and I want to have access
to task instances from it. So that I can reuse all existing operators e.g. DockerOperator
and access its fields like image, command, volumes and transform them to mesos.
> This can be done by changing `def execute_async(self, key, command, queue=None):` in
`BaseExecutor`.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message