Repository navigation
Avoid loading timetables for dags in Execution API endpoints - #75765
Merged
Merged
Conversation
For a few reasons/places now in the Exec API we now need the serialized dag, but we don't need the timetable (which could involve loading) plugins or user code. This should let the ExecAPI run without user code if a deployment admin wishes to try that.
shahar1
approved these changes
Oct 27, 2026
vatsrahul1001
approved these changes
Oct 27, 2026
feluelle
approved these changes
Oct 27, 2026
Contributor
|
The re-run of the jobs stopped by EC2 Spot interruptions finished: attempt 3 failed. |
`weight_rule` on SerializedDag is already a property that decodes/inflates strings into the object
kaxil
reviewed
Oct 27, 2026
jason810496
reviewed
Oct 28, 2026
jason810496
left a comment
jason810496
left a comment
Member
There was a problem hiding this comment.
#75842 should solve the CI failure (thanks @amoghrajesh for the info), will rebase this PR once #75842 get merged.
Contributor
Backport successfully created: v3-4-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
vatsrahul1001
pushed a commit
that referenced
this pull request
Oct 28, 2026
…nts (#75765) (#75846) * Avoid loading timetables for dags in Execution API endpoints For a few reasons/places now in the Exec API we now need the serialized dag, but we don't need the timetable (which could involve loading) plugins or user code. This should let the ExecAPI run without user code if a deployment admin wishes to try that. * Stop eagerly decoding custom weight_rules `weight_rule` on SerializedDag is already a property that decodes/inflates strings into the object * Fix reviews * fixup! Avoid loading timetables for dags in Execution API endpoints --------- (cherry picked from commit 402ab11) Co-authored-by: Ash Berlin-Taylor <ash@astronomer.io> Co-authored-by: Jason(Zhe-You) Liu <68415893+jason810496@users.noreply.github.com>
1 task done
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
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.
For a few reasons/places now in the Exec API we now need the serialized
dag, but we don't need the timetable (which could involve loading) plugins
or user code.
This should let the ExecAPI run without user code if a deployment admin
wishes to try that.
Spotted by @feluelle
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.