From 12545f63e0e990dab0cd3edb2e83725eb0ff44b1 Mon Sep 17 00:00:00 2001 From: Siddique Ahmad Date: Tue, 5 Mar 2024 21:53:08 +0500 Subject: [PATCH 1/4] Update scheduling.rst schedule is right parameter name --- docs/configuration/scheduling.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration/scheduling.rst b/docs/configuration/scheduling.rst index de21f8495..738031848 100644 --- a/docs/configuration/scheduling.rst +++ b/docs/configuration/scheduling.rst @@ -50,7 +50,7 @@ Then, you can use Airflow's data-aware scheduling capabilities to schedule ``my_ project_two = DbtDag( # ... - schedule_interval=[get_dbt_dataset("my_conn", "project_one", "my_model")], + schedule=[get_dbt_dataset("my_conn", "project_one", "my_model")], dbt_project_name="project_two", ) From bbe13f747b1400cb0c1f768e82fff4693e026062 Mon Sep 17 00:00:00 2001 From: Siddique Ahmad Date: Mon, 11 Mar 2024 07:37:53 +0500 Subject: [PATCH 2/4] Proper comment added for different airflow versions --- docs/configuration/scheduling.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/configuration/scheduling.rst b/docs/configuration/scheduling.rst index 738031848..046e5060c 100644 --- a/docs/configuration/scheduling.rst +++ b/docs/configuration/scheduling.rst @@ -49,7 +49,9 @@ Then, you can use Airflow's data-aware scheduling capabilities to schedule ``my_ ) project_two = DbtDag( - # ... + # for airflow >=2.3 + #schedule_interval=[get_dbt_dataset("my_conn", "project_one", "my_model")], + # for airflow > 2.3 schedule=[get_dbt_dataset("my_conn", "project_one", "my_model")], dbt_project_name="project_two", ) From 37275c64bb7d3127cc5c0ab53f2f34be42b966bf Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Mon, 11 Mar 2024 02:39:04 +0000 Subject: [PATCH 3/4] =?UTF-8?q?=F0=9F=8E=A8=20[pre-commit.ci]=20Auto=20for?= =?UTF-8?q?mat=20from=20pre-commit.com=20hooks?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/configuration/scheduling.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration/scheduling.rst b/docs/configuration/scheduling.rst index 046e5060c..e68b4b880 100644 --- a/docs/configuration/scheduling.rst +++ b/docs/configuration/scheduling.rst @@ -50,7 +50,7 @@ Then, you can use Airflow's data-aware scheduling capabilities to schedule ``my_ project_two = DbtDag( # for airflow >=2.3 - #schedule_interval=[get_dbt_dataset("my_conn", "project_one", "my_model")], + # schedule_interval=[get_dbt_dataset("my_conn", "project_one", "my_model")], # for airflow > 2.3 schedule=[get_dbt_dataset("my_conn", "project_one", "my_model")], dbt_project_name="project_two", From 7aa02757d097d53b4d2dc81ce598b4a3984584d3 Mon Sep 17 00:00:00 2001 From: Siddique Ahmad Date: Thu, 4 Apr 2024 11:14:20 +0500 Subject: [PATCH 4/4] Change param name to schedule schedule_interval is deprecated and will be removed so updating param name --- docs/configuration/scheduling.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/configuration/scheduling.rst b/docs/configuration/scheduling.rst index e68b4b880..a1275ee19 100644 --- a/docs/configuration/scheduling.rst +++ b/docs/configuration/scheduling.rst @@ -17,7 +17,7 @@ To schedule a dbt project on a time-based schedule, you can use Airflow's schedu jaffle_shop = DbtDag( # ... start_date=datetime(2023, 1, 1), - schedule_interval="@daily", + schedule="@daily", ) @@ -45,12 +45,12 @@ Then, you can use Airflow's data-aware scheduling capabilities to schedule ``my_ project_one = DbtDag( # ... start_date=datetime(2023, 1, 1), - schedule_interval="@daily", + schedule="@daily", ) project_two = DbtDag( - # for airflow >=2.3 - # schedule_interval=[get_dbt_dataset("my_conn", "project_one", "my_model")], + # for airflow <=2.3 + # schedule=[get_dbt_dataset("my_conn", "project_one", "my_model")], # for airflow > 2.3 schedule=[get_dbt_dataset("my_conn", "project_one", "my_model")], dbt_project_name="project_two",