Move import error deletion migration to separate file #51565
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boring-cyborg
bot
added
area:db-migrations
uranusjr
approved these changes
Jun 11, 2025
Lee-W
approved these changes
Jun 11, 2025
This will be more beneficial being in a new migration file than in old file so that upgrading to the new version fixes it for all. Added it to 3.0.3 release
ephraimbuddy
force-pushed
the
move-import-error-del
branch
from
e5ee6e1 to
877587d
Compare
|
Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions. |
ephraimbuddy
added
the
backport-to-v3-1-test
choo121600
pushed a commit
to choo121600/airflow
that referenced
this pull request
Jun 14, 2025
ephraimbuddy
added a commit
to astronomer/airflow
that referenced
this pull request
Jun 19, 2025
(cherry picked from commit 95a1e77)
potiuk
pushed a commit
that referenced
this pull request
Jun 21, 2025
* Clean up import error records during DB migration (#51472) * Clean up import error records during DB migration This PR adds an SQL to clean up import errors during add bundle migration The bug we found was that import errors with null bundle_name field doesn't get cleared after migration. The processor manager's `clear_orphaned_import_errors` method filters by bundle_name and that makes the import errors with null bundle_name not to be included in the method's result * fixup! Clean up import error records during DB migration (cherry picked from commit 7ed78dc) * Move import error deletion migration to separate file (#51565) (cherry picked from commit 95a1e77)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will be more beneficial being in a new migration file than in old file so that upgrading to the new version fixes it for all. Added it to 3.0.3 release