Description
On this doc page, Airflow explicitly says all datasets need to be updated before a DAG runs is triggered.
When using datasets, in this first release (v2.4) waiting for all datasets in the list to be updated is the only option when multiple datasets are consumed by a DAG. A later release may introduce more fine-grained options allowing for greater flexibility.
I would like to see the schedule param logic configurable so that all or any dataset being updated triggers a DAG run.
Use case/motivation
Configurable so that a DAG run is triggered when either all or any dataset is updated.
To keep the API consistent, code changes would keep all as the default functionality.
Related issues
Tangential, but not directly related
Are you willing to submit a PR?
Code of Conduct
Description
On this doc page, Airflow explicitly says all datasets need to be updated before a DAG runs is triggered.
I would like to see the
scheduleparam logic configurable so that all or any dataset being updated triggers a DAG run.Use case/motivation
Configurable so that a DAG run is triggered when either all or any dataset is updated.
To keep the API consistent, code changes would keep
allas the default functionality.Related issues
Tangential, but not directly related
Are you willing to submit a PR?
Code of Conduct