You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/08/06 19:17:00 UTC
[jira] [Commented] (AIRFLOW-4443) Update LatestOnlyOperator
docstring to clarify behavior during externally triggered dagrun
[ https://issues.apache.org/jira/browse/AIRFLOW-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16901401#comment-16901401 ]
ASF subversion and git services commented on AIRFLOW-4443:
----------------------------------------------------------
Commit 56939c9bfc17079770abe12036e0fd15fb68c759 in airflow's branch refs/heads/master from kyle hausmann
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=56939c9 ]
[AIRFLOW-4443] Document LatestOnly behavior for external trigger (#5214)
> 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
> Priority: Minor
>
> 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.14#76016)