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

Evaluate DB migration restriction when upgrading to AF 3 #41643

Open
Tracked by #39593
kaxil opened this issue Aug 21, 2024 · 2 comments
Open
Tracked by #39593

Evaluate DB migration restriction when upgrading to AF 3 #41643

kaxil opened this issue Aug 21, 2024 · 2 comments
Labels
airflow3.0:breaking Candidates for Airflow 3.0 that contain breaking changes area:db-migrations PRs with DB migration
Milestone

Comments

@kaxil
Copy link
Member

kaxil commented Aug 21, 2024

As part of #41120 , we pruned the Database migration files. This change means that users will have to upgrade to Airflow 2.10 before they can upgrade to Airflow 3.0. If a user tried to migrate directly from 2.7 to 3.0 -- they might get an Alembic revision error.

We should re-evaluate this before we release Airflow 3.0 and clearly document the expectation so users don't run into troubles when upgrading to 3.0 from lower Airflow versions.

@kaxil kaxil mentioned this issue Aug 21, 2024
10 tasks
@kaxil kaxil added the airflow3.0:breaking Candidates for Airflow 3.0 that contain breaking changes label Aug 21, 2024
@kaxil kaxil added this to the Airflow 3.0.0 milestone Aug 21, 2024
@dosubot dosubot bot added the area:db-migrations PRs with DB migration label Aug 21, 2024
@kaxil
Copy link
Member Author

kaxil commented Aug 21, 2024

fyi @ephraimbuddy

@ashb
Copy link
Member

ashb commented Aug 21, 2024

they might get an Alembic revision error.

They will get an alembic version error ERROR [alembic.util.messaging] Can't locate revision identified by ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
airflow3.0:breaking Candidates for Airflow 3.0 that contain breaking changes area:db-migrations PRs with DB migration
Projects
None yet
Development

No branches or pull requests

2 participants