You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Tongzhou Wang (JIRA)" <ji...@apache.org> on 2016/08/02 23:55:20 UTC
[jira] [Commented] (AIRFLOW-389) Support more general and
customizable trigger rule options
[ https://issues.apache.org/jira/browse/AIRFLOW-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405048#comment-15405048 ]
Tongzhou Wang commented on AIRFLOW-389:
---------------------------------------
I will investigate into this, and come up with a design doc.
> Support more general and customizable trigger rule options
> ----------------------------------------------------------
>
> Key: AIRFLOW-389
> URL: https://issues.apache.org/jira/browse/AIRFLOW-389
> Project: Apache Airflow
> Issue Type: Improvement
> Affects Versions: Airflow 2.0
> Reporter: Tongzhou Wang
> Assignee: Tongzhou Wang
>
> Currently, the trigger rule options in Airflow are very limited. For example, it is difficult to let a task trigger when the upstream either failed or succeeded (but not upstream_failed).
> We should support more general and more customizable trigger rule options.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)