collinmcnulty opened a new pull request #18071: URL: https://github.com/apache/airflow/pull/18071
The example dags all use a dynamic start date, but this is not good practice. In my experience, many people new to Airflow continue to use dynamic start dates in their real dags and it causes them problems. For example, they get into the habit of using `days_ago(1)` and that works for daily dags but not for anything less frequent than that. I assume the example dags use dynamic start date to keep from spawning many dagruns for anyone who chooses to run them. I propose that `catchup=False` be used for that purpose instead. This PR only covers the core airflow example dags, not all the providers. -- 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]
