Get last run info one dag at a time #59376
Open
+35
−63
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
dstandish
force-pushed
the
handle-one-dag-at-a-time-re-last-run-info
branch
3 times, most recently
from
e8c4c60 to
52a65e2
Compare
dstandish
requested review from
ephraimbuddy and
jedcunningham
as code owners
This may make it easier when handling partition-driven dags differently from non-partition-driven.
dstandish
force-pushed
the
handle-one-dag-at-a-time-re-last-run-info
branch
from
b9ff78d to
c57b7b2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 may make it easier when handling partition-driven dags differently from non-partition-driven.
But in any case, (1) it makes the code substantially simpler and (2) most of the time it's one dag per file / process anyway. Need to test to see if any meaningful impact.