From 6ee8c3734693bf7c0ffd50c423530724169f424b Mon Sep 17 00:00:00 2001 From: Marty Woodlee Date: Thu, 25 Jun 2015 12:14:56 -0500 Subject: [PATCH] Clarify the function of wait_for_downstream --- airflow/models.py | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/airflow/models.py b/airflow/models.py index 0e0c43e0e5..26965709cb 100644 --- a/airflow/models.py +++ b/airflow/models.py @@ -962,11 +962,11 @@ class BaseOperator(object): sequentially while relying on the previous task's schedule to succeed. The task instance for the start_date is allowed to run. :type depends_on_past: bool - :param wait_for_downstream: when set to true, the task instances - of task X will wait for the dependencies of the previous instance - of task X to finish before it moves on the to next schedule. - This is useful if the different instances of a task X alter - the same asset, and this asset is used by the dependencies of task X. + :param wait_for_downstream: when set to true, an instance of task + X will wait for the dependents of the previous instance of task X + to finish successfully before it runs. This is useful if the + different instances of a task X alter the same asset, and this asset + is used by the dependencies of task X. :type wait_for_downstream: bool :param queue: which queue to target when running this job. Not all executors implement queue management, the CeleryExecutor