-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
[AIRFLOW-2870] Use abstract TaskInstance for migration #3720
Conversation
8432654
to
0d85793
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.
LGTM
0d85793
to
8c55dfa
Compare
Codecov Report
@@ Coverage Diff @@
## master #3720 +/- ##
=======================================
Coverage 77.63% 77.63%
=======================================
Files 204 204
Lines 15800 15800
=======================================
Hits 12267 12267
Misses 3533 3533 Continue to review full report at Codecov.
|
Clever approach; thanks for taking this on @bolkedebruin On attempting
Looks like we also need the "try_number" column on the migration version of the model:
|
Ah let me fix that |
If we use the full model for migration it can have columns added that are not available yet in the database. Using an abstraction ensures only the columns that are required for data migration are present.
8c55dfa
to
311bc91
Compare
@gwax done. PTAL |
That works for me now. ! |
If we use the full model for migration it can have columns added that are not available yet in the database. Using an abstraction ensures only the columns that are required for data migration are present. (cherry picked from commit 546f1cd) Signed-off-by: Bolke de Bruin <[email protected]>
If we use the full model for migration it can have columns added that are not available yet in the database. Using an abstraction ensures only the columns that are required for data migration are present. (cherry picked from commit 546f1cd) Signed-off-by: Bolke de Bruin <[email protected]> (cherry picked from commit 95aa49a) Signed-off-by: Bolke de Bruin <[email protected]>
If we use the full model for migration it can have columns added that are not available yet in the database. Using an abstraction ensures only the columns that are required for data migration are present.
If we use the full model for migration it can have columns added that are not available yet in the database. Using an abstraction ensures only the columns that are required for data migration are present.
If we use the full model for migration it can have columns added that are not available yet in the database. Using an abstraction ensures only the columns that are required for data migration are present. (cherry picked from commit 546f1cd) Signed-off-by: Bolke de Bruin <[email protected]> (cherry picked from commit 95aa49a) Signed-off-by: Bolke de Bruin <[email protected]>
Make sure you have checked all steps below.
Jira
Description
If we use the full model for migration it can have columns
added that are not available yet in the database. Using
an abstraction ensures only the columns that are required
for data migration are present.
Tests
Db migration
Commits
@ashb @gwax PTAL
Documentation
Code Quality
git diff upstream/master -u -- "*.py" | flake8 --diff