You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by je...@apache.org on 2022/09/23 03:19:27 UTC

[airflow] 06/13: Fix example_datasets dag names (#26495)

This is an automated email from the ASF dual-hosted git repository.

jedcunningham pushed a commit to branch v2-4-test
in repository https://gitbox.apache.org/repos/asf/airflow.git

commit aa4f1c4028730ecd67eb51710ba8ed18b57f0ebc
Author: pierrejeambrun <pi...@gmail.com>
AuthorDate: Mon Sep 19 20:56:37 2022 +0200

    Fix example_datasets dag names (#26495)
    
    (cherry picked from commit e6838c92df6904e8f8f33951108f09ed5c590c72)
---
 airflow/example_dags/example_datasets.py | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/airflow/example_dags/example_datasets.py b/airflow/example_dags/example_datasets.py
index 1d11cf1b76..0da33f5000 100644
--- a/airflow/example_dags/example_datasets.py
+++ b/airflow/example_dags/example_datasets.py
@@ -21,20 +21,20 @@ Notes on usage:
 
 Turn on all the dags.
 
-DAG example_dataset_dag1 should run because it's on a schedule.
+DAG dataset_produces_1 should run because it's on a schedule.
 
-After example_dataset_dag1 runs, example_dataset_dag3_req_dag1 should be triggered immediately
-because its only dataset dependency is managed by example_dataset_dag1.
+After dataset_produces_1 runs, dataset_consumes_1 should be triggered immediately
+because its only dataset dependency is managed by dataset_produces_1.
 
-No other dags should be triggered.  Note that even though example_dataset_dag4_req_dag1_dag2 depends on
-the dataset in example_dataset_dag1, it will not be triggered until example_dataset_dag2 runs
-(and example_dataset_dag2 is left with no schedule so that we can trigger it manually).
+No other dags should be triggered.  Note that even though dataset_consumes_1_and_2 depends on
+the dataset in dataset_produces_1, it will not be triggered until dataset_produces_2 runs
+(and dataset_produces_2 is left with no schedule so that we can trigger it manually).
 
-Next, trigger example_dataset_dag2.  After example_dataset_dag2 finishes,
-example_dataset_dag4_req_dag1_dag2 should run.
+Next, trigger dataset_produces_2.  After dataset_produces_2 finishes,
+dataset_consumes_1_and_2 should run.
 
-Dags example_dataset_dag5_req_dag1_D and example_dataset_dag6_req_DD should not run because they depend on
-datasets that never get updated.
+Dags dataset_consumes_1_never_scheduled and dataset_consumes_unknown_never_scheduled should not run because
+they depend on datasets that never get updated.
 """
 from __future__ import annotations