From a31b9e6c281ebcc7ef9c18d62e3455e443c6143c Mon Sep 17 00:00:00 2001 From: Siddique Ahmad Date: Sat, 20 Apr 2024 23:53:50 +0500 Subject: [PATCH] docs: use of datasets for airflow >= 2.4 (#879) schedule is right parameter name ## Description schedule is right parameter name. ## Related Issue(s) ## Breaking Change? ## Checklist - [ ] I have made corresponding changes to the documentation (if required) - [ ] I have added tests that prove my fix is effective or that my feature works --------- Co-authored-by: Tatiana Al-Chueyr Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> --- docs/configuration/scheduling.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/configuration/scheduling.rst b/docs/configuration/scheduling.rst index de21f8495..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,14 @@ 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( - # ... - 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", )