You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Kyle Hausmann (JIRA)" <ji...@apache.org> on 2019/04/30 18:06:00 UTC

[jira] [Created] (AIRFLOW-4443) Update LatestOnlyOperator docstring to clarify behavior during externally triggered dagrun

Kyle Hausmann created AIRFLOW-4443:
--------------------------------------

             Summary: Update LatestOnlyOperator docstring to clarify behavior during externally triggered dagrun
                 Key: AIRFLOW-4443
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4443
             Project: Apache Airflow
          Issue Type: Improvement
            Reporter: Kyle Hausmann


A LatestOnlyOperator task will never skip downstream tasks if run in an externally triggered dagrun. This is probably reasonable–the software is not making assumptions about the trigger-er's intention when creating an unscheduled dagrun, and in that agnostic state, the default behavior would be to not skip any tasks.

However, that rationale may not be obvious to an enduser, who may be confused why a latest-only task in an externally triggered dagrun with an execution_date in the past is not skipping downstream tasks.

The docstring for the LatestOnlyOperator should clarify the operator's behavior in this scenario.

I will be submitting a very small PR with updated docstring shortly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)