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 GitHub Bot (JIRA)" <ji...@apache.org> on 2019/04/30 18:31: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=16830557#comment-16830557 ]
ASF GitHub Bot commented on AIRFLOW-4443:
-----------------------------------------
khgitting commented on pull request #5214: [AIRFLOW-4443] Document behavior of LatestOnlyOperator for externally triggered dagrun
URL: https://github.com/apache/airflow/pull/5214
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.
This PR updates the docstring for the LatestOnlyOperator to clarify
the operator's behavior in this scenario.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> 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.3#76005)