-
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
Ensure that dag_id, run_id and execution_date are non-null on DagRun #18804
Conversation
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.
I can't find 306a0384de71
migration, did you miss a file?
🤦 |
c845434
to
3d12d07
Compare
airflow/migrations/versions/306a0384de71_make_dagrun_id_columns_non_nullable.py
Outdated
Show resolved
Hide resolved
This didn't apply on mysql, so rather than creating the FK in one migration, then dropping it to alter the column types and then recreating it, we should just change the column types before hand. |
These _should_ be non-nullable, and are always created as such. Without this it was possible that someone had manually edited it which caused problems with the TaskInstance FK migration not applying correctly.
acce77c
to
fc1f5be
Compare
I am guessing this will be merged into |
actually we keep on moving v2-2-test with main but generally speaking this one is marked for 2.2.0 so yeah - it will land in v2-2-test |
Only after we cut an RC the branches will diverge |
Yup this is now already part of v2-2-test and part of 2.2.0 rc1. https://github.com/apache/airflow/commits/v2-2-test |
These should be non-nullable, and are always created as such. Without
this it was possible that someone had manually edited it which caused
problems with the TaskInstance FK migration not applying correctly.
Closes #18801
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.