Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
Date: Thu, 30 Jun 2016 21:19:10 +0000 (UTC)
From: "Jeremiah Lowin (JIRA)" <jira@apache.org>
To: commits@airflow.incubator.apache.org
Message-ID: <JIRA.12967240.1462923230000.8030.1467321550145@Atlassian.JIRA>
In-Reply-To: <JIRA.12967240.1462923230000@Atlassian.JIRA>
References: <JIRA.12967240.1462923230000@Atlassian.JIRA> <JIRA.12967240.1462923230021@arcas>
Subject: [jira] [Updated] (AIRFLOW-100) Add flexibility to
 ExternalTaskSensor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 30 Jun 2016 21:19:15 -0000


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

Jeremiah Lowin updated AIRFLOW-100:
-----------------------------------
    External issue URL: https://github.com/apache/incubator-airflow/pull/1641

> Add flexibility to ExternalTaskSensor
> -------------------------------------
>
>                 Key: AIRFLOW-100
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-100
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: operators
>            Reporter: Jeremiah Lowin
>            Assignee: Jeremiah Lowin
>            Priority: Minor
>              Labels: operator
>
> The ExternalTaskSensor defaults to sensing tasks with the same {{execution_date}} as it does, and has an {{execution_delta}} parameter for looking back farther in time. However, this doesn't support the case where the sensing task has a smaller schedule_interval than the target task.
> For example, if the ETS were run every hour, one couldn't use a fixed {{execution_delta}} to sense a task that only ran daily (since each instance of the ETS would need a different execution_delta). 
> However, a Daily task can wait for multiple hourly tasks, because it knows in advance that it needs 24 ETS's with deltas == range(24).
> Concrete suggestion:
> - add a param ({{execution_delta_fn}}?) that takes in the current execution_date and is expected to return the desired sense date (for example, it could always return midnight of the previous day, no matter what the ETS was executed).
> cc [~criccomini]


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