Don't import/load executor if it's not necessary#55742
Merged
vincbeck merged 1 commit intoapache:mainfrom Sep 17, 2025
Merged
Conversation
If we are skipping log serving there is no need to import/load the executor to check if it supports log serving.
ramitkataria
approved these changes
Sep 16, 2025
vincbeck
approved these changes
Sep 17, 2025
kaxil
pushed a commit
that referenced
this pull request
Sep 18, 2025
If we are skipping log serving there is no need to import/load the executor to check if it supports log serving. (cherry picked from commit 7fee3e9)
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
5 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.
If we are skipping log serving there is no need to import/load the executor to check if it supports log serving.
Discovered this small optimization when working on a related bit of code.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.