Prevent legacy hybrid executors to be running in Airflow 3 - 2nd attempt #51760
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:providers
provider:celery
provider:cncf-kubernetes
jason810496
approved these changes
Jun 15, 2025
Member
|
Nice! |
RoyLee1224
pushed a commit
to RoyLee1224/airflow
that referenced
this pull request
Jun 21, 2025
jscheffl
deleted the
bugfix/prevent-old-hybrid-executors-to-run-in-airflow-3-v2
branch
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.
After #51733 and in testing the released packages I noticed that the check in
start()is never reached because the failure of Airflow 3 is already during construction time.So this PR is a second attempt to provide a clear error message - now in constructor of the class. Slightly needed to adjust constructor and also added a pseudo check in the version preventing mypy compliants later if passed backend executors are not provided which is only happening in Airflow 3.