widewing opened a new issue, #54285: URL: https://github.com/apache/airflow/issues/54285
### Apache Airflow version 3.0.3 ### If "Other Airflow 2 version" selected, which one? _No response_ ### What happened? It seems the DAG version is changed whenever any field is changed. But for our use case we want to have a limited catchup period, so we set `start_date=datetime.now()-timedelta(hours=1)`, which cause the dag version keep changing and dag_version table to grow over time. ### What you think should happen instead? I think we should carefully define the dag version. User should also have control of their dag's version. Also we should only keep dag version to a small number to avoid infinite grow of the table and potential performance issue. ### How to reproduce Set dynamic start_date ### Operating System linux ### Versions of Apache Airflow Providers _No response_ ### Deployment Other 3rd-party Helm chart ### Deployment details _No response_ ### Anything else? _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
