potiuk commented on issue #35998: URL: https://github.com/apache/airflow/issues/35998#issuecomment-1837425016
What you see is likely effect of serialization how it was implemented 2.5 years ago - with thousands of bug fixes released since - including tens of them released in the 2.1 line you are using (2.1.3. and 2.1.4). hash calculation for Airflow only uses those fields: ``` _comps = { "task_id", "dag_id", "owner", "email", "email_on_retry", "retry_delay", "retry_exponential_backoff", "max_retry_delay", "start_date", "end_date", "depends_on_past", "wait_for_downstream", "priority_weight", "sla", "execution_timeout", "on_execute_callback", "on_failure_callback", "on_success_callback", "on_retry_callback", "do_xcom_push", } ``` But since 2.1.2 there were probably 10s of changes in this area. > Please advise more. Upgrade to latest version of Airflow. This is the fastest way. I you want to see if there are any bugfixes related to serialization, to be sure that it is worth it - you can go through release notes https://airflow.apache.org/docs/apache-airflow/stable/release_notes.html and check the few thousands of fixes since, but I strongly advice you to just upgrade - even if there was a bug in the hash implementation back then, the only way to fix it is to upgrade anyway, so you can safe a lot of time on looking by just upgrading. If you see similar problems after upgrading. please report it here. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org