Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop reserializing DAGs during db migration #45362

Merged

Conversation

jedcunningham
Copy link
Member

At first, this may seem strange, but we already have to deal with older versions of serialized DAGs - so the necessity of reserializing during migrations isn't there any longer. The DAG processor can simply do it once Airflow has started back up.p

I've opened #45361 as a check point, once the dust has settled, to see if we need to add it back.

At first, this may seem strange, but we already have to deal with older
versions of serialized DAGs - so the necessity of reserializing during
migrations isn't there any longer. The DAG processor can simply do it
once Airflow has started back up.
@jedcunningham
Copy link
Member Author

Failure is unrelated (see #45329).

@jedcunningham jedcunningham merged commit 9776843 into apache:main Jan 2, 2025
65 of 66 checks passed
@jedcunningham jedcunningham deleted the stop_reserializing_during_migration branch January 2, 2025 22:53
LefterisXefteris pushed a commit to LefterisXefteris/airflow that referenced this pull request Jan 5, 2025
At first, this may seem strange, but we already have to deal with older
versions of serialized DAGs - so the necessity of reserializing during
migrations isn't there any longer. The DAG processor can simply do it
once Airflow has started back up.
agupta01 pushed a commit to agupta01/airflow that referenced this pull request Jan 6, 2025
At first, this may seem strange, but we already have to deal with older
versions of serialized DAGs - so the necessity of reserializing during
migrations isn't there any longer. The DAG processor can simply do it
once Airflow has started back up.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

3 participants