Make SparkSubmitOperator durable execution inert below Airflow 3.3 - #71534
Merged
amoghrajesh merged 2 commits intoAug 18, 2026
Merged
amoghrajesh merged 2 commits into
amoghrajesh merged 2 commits into
Conversation
Contributor
Author
|
cc @nailo2c would love to get a review if you can |
eladkal
approved these changes
Aug 17, 2026
91 tasks
imrichardwu
pushed a commit
to imrichardwu/airflow
that referenced
this pull request
Sep 11, 2026
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.
Was generative AI tooling used to co-author this PR?
durablewas already wired straight into the operator's YARN cluster-mode validation and, before this, was silently accepted below 3.3 with no signal that it does nothing there since this provider still supports Airflow 2.11 through 3.x and ResumableJobMixin (and the task state store it relies on) only exists on 3.3+.The compat stub now warns if durable is set explicitly below 3.3 and always resolves it to False, matching the same fix already applied to #71531
reconnect_on_retry-- the parameter's original name, introduced in the same PR as ResumableJobMixin itself and renamed to durable almost immediately -- gets a plain map-and-deprecate rather than the legacy-flag treatment Glue and KPO need. It was never a distinct pre-existing mechanism with its own below-3.3 behavior to preserve, so telling a caller on any version to "use durable instead" is not bad advice the way it would be for a flag with real legacy behavior. Thedeprecation warning fires on every Airflow version regardless, since removal happens on this provider's own release schedule, not the caller's.
The YARN
yarn_track_via_rm_apirequirement needed no code change: it already readsself.durable, so once durable is properly inert below 3.3, the requirement naturally stops applying there too -- there's no durable-execution prerequisite to enforce when durable execution itself isn't active.{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.