GitHub user ecodina added a comment to the discussion: Dag Versioning keeps increasing
Thanks! First of all, I ran this query: ```sql select dag_code.* from dag_code,dag_version where dag_code.dag_version_id =dag_version.id and dag_code.dag_id ='my_dag' order by dag_version.version_number; ``` What I saw is that the source_code_hash didn't change at all between versions: <img width="273" height="509" alt="image" src="https://github.com/user-attachments/assets/7b3a28f4-84cb-46ef-9cf7-2ebdb223b099"; /> I then chose 2 versions (`019d6d4d-db14-78f1-ada6-300c326badd6` and `019d6d4e-d09d-7cdf-b97e-207399e21872`) that had been generated 2 minutes apart on the 8th April. With that, I saw that there was a difference in the `data` column for the task. One version had: ```json "template_fields":[ "command", "env", "slurm_options", "submit_as_user" ], ``` and the other: ```json "template_fields":[ "command", "env", "slurm_options", "submit_as_user", "cluster" ], cluster:"XXX" ``` The parameter "cluster" was added into the template_fields for the SlurmOperator available in our provider. We have 2 dag processor running, and I believe one of them is/was using an old version of the provider. This is weird, since we manage Docker Swarm using Portainer and redeploy using "Pull and Redeploy", which should restart all services and tasks. Does my hypothesis make sense? GitHub link: https://github.com/apache/airflow/discussions/66103#discussioncomment-16787368 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
