ephraimbuddy opened a new pull request, #53820:
URL: https://github.com/apache/airflow/pull/53820

   It seemed simpler to reserialize the DAGs and update the task instances 
directly, so that's what I did here. I'm slightly unsure if this could lead to 
failures during reserialization or cause performance issues.
   
   An alternative would have been to manually create entries for 
serialized_dag, dag_version, and dag_code before updating the TIs, but that 
felt more complex.
   
   The issue here is that, upgrades from AF2 fails due to the TIs not been 
associated with dag_versions. The issue mainly affects users upgrading from 
Airflow 2, since in Airflow 3 the dag_version table is already populated for 
all DAGs.
   


-- 
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]

Reply via email to