This is an automated email from the ASF dual-hosted git repository. jedcunningham pushed a commit to branch v2-2-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit a519e53ddee5675402c091c1e99fe1643a968e87 Author: Lucia Kasman <38845383+luciakas...@users.noreply.github.com> AuthorDate: Thu Feb 3 15:10:27 2022 -0300 Docs: Fix task order in overview example (#21282) (cherry picked from commit 1ba83c01b2b466ad5a76a453e5f6ee2884081e53) --- docs/apache-airflow/concepts/overview.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/apache-airflow/concepts/overview.rst b/docs/apache-airflow/concepts/overview.rst index fd862ea..567c3c8 100644 --- a/docs/apache-airflow/concepts/overview.rst +++ b/docs/apache-airflow/concepts/overview.rst @@ -65,12 +65,12 @@ Control Flow :doc:`tasks` have dependencies declared on each other. You'll see this in a DAG either using the ``>>`` and ``<<`` operators:: first_task >> [second_task, third_task] - third_task << fourth_task + fourth_task << third_task Or, with the ``set_upstream`` and ``set_downstream`` methods:: first_task.set_downstream([second_task, third_task]) - third_task.set_upstream(fourth_task) + fourth_task.set_upstream(third_task) These dependencies are what make up the "edges" of the graph, and how Airflow works out which order to run your tasks in. By default, a task will wait for all of its upstream tasks to succeed before it runs, but this can be customized using features like :ref:`Branching <concepts:branching>`, :ref:`LatestOnly <concepts:latest-only>`, and :ref:`Trigger Rules <concepts:trigger-rules>`.