-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
fix(migration): fix dataset to asset migration typo #43245
fix(migration): fix dataset to asset migration typo #43245
Conversation
c6413e0
to
e658a93
Compare
db96b28
to
7365f9c
Compare
Why is it Also running |
Those are fks from Airflow 2.10 that we need to rename.
Thanks for reminding me! There's yet another issue, but somewhat related. Fixed in this PR |
7365f9c
to
bf2fa09
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be backported, right?
0026 yes, 0040 no |
…g_fkey. thus, we need to use dsdar_dag_fkey in migration files
bf2fa09
to
628fcf9
Compare
backport pr #43314 |
* fix(migration): fix dataset to asset migration typo * fix(migrations): dsdar_dag_id_fkey was accidentally named as dsdar_dag_fkey. thus, we need to use dsdar_dag_fkey in migration files
* fix(migration): fix dataset to asset migration typo * fix(migrations): dsdar_dag_id_fkey was accidentally named as dsdar_dag_fkey. thus, we need to use dsdar_dag_fkey in migration files
* fix(migration): fix dataset to asset migration typo * fix(migrations): dsdar_dag_id_fkey was accidentally named as dsdar_dag_fkey. thus, we need to use dsdar_dag_fkey in migration files
Closes: #43226
Why
dsdar_dataset_alias_fkey
was accidentally named asdsdar_dataset_fkey
in migration files^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.