Remove reparse on DAG depending on asset alias #44866
Merged
+0
−7
Conversation
This file contains 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
I suspect we no longer need this since alias resolution now happens very late in the scheduling process. A DAG *should* be able to automatically understand the alias is resolved without a reparse after refactorings introduced in cccc933.
55990f4 to
1ce03d7
Compare
hussein-awala
approved these changes
Dec 12, 2024
|
@uranusjr would like to confirm whether it works on your local. I tried with commit |
|
Still some problems. Don’t merge this yet. |
|
I can’t come up with a good way to test this (our test setup does not lend well toward real scheduler isolation). I’m going to just cross fingers and merge this if @Lee-W does not reject. |
Lee-W
approved these changes
Dec 16, 2024
LefterisXefteris
pushed a commit
to LefterisXefteris/airflow
that referenced
this pull request
Jan 5, 2025
I suspect we no longer need this since alias resolution now happens very late in the scheduling process. A DAG *should* be able to automatically understand the alias is resolved without a reparse after refactorings introduced in cccc933.
got686-yandex
pushed a commit
to got686-yandex/airflow
that referenced
this pull request
Jan 30, 2025
I suspect we no longer need this since alias resolution now happens very late in the scheduling process. A DAG *should* be able to automatically understand the alias is resolved without a reparse after refactorings introduced in cccc933.
jedcunningham
added a commit
to astronomer/airflow
that referenced
this pull request
Mar 13, 2025
This functionality was removed in apache#44866, but the methods weren't removed. The reparse functionality is being refactored, so removing them is easier than repairing them.
kaxil
pushed a commit
that referenced
this pull request
Mar 13, 2025
This functionality was removed in #44866, but the methods weren't removed. The reparse functionality is being refactored, so removing them is easier than repairing them.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I suspect we no longer need this since alias resolution now happens very late in the scheduling process. A DAG should be able to automatically understand the alias is resolved without a reparse after refactorings introduced in cccc933.
Let’s see what CI thinks.