BasPH commented on PR #38168: URL: https://github.com/apache/airflow/pull/38168#issuecomment-2002220378
@eladkal please elaborate on "holistic approach"? I see this PR as a temporary solution until Airflow 3. What I expect `catchup` to do when unpausing a DAG: - `catchup=True` executes all historical DAG runs that weren't executed while the DAG was paused - `catchup=False` waits for the first interval to complete when unpaused, e.g. waits till 00:00 with a `"@daily"` schedule You currently immediately execute one DAG run when unpausing with a past `start_date` + `catchup=False`. This is causing a lot of trouble, especially during migrations where sometimes hundreds or even thousands of DAGs have to be unpaused. This is very counterintuitive. I think having yet another parameter as suggested in https://github.com/apache/airflow/pull/35392 is unnecessary. However, since changing this behaviour would be considered a breaking change, it can only first be changed in Airflow 3.0. This PR adds a config that's also deprecated at the same time which enables this behaviour as a bridge solution for future Airflow 2.* versions. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
