Repository navigation
Add EmrServerlessStopSessionOperator to Amazon provider - #74870
Merged
vincbeck merged 1 commit intoOct 19, 2026
Merged
Conversation
Dags that start an EMR Serverless interactive session need a way to end it as soon as their work is done rather than relying on the session's idle timeout. Stopping follows the same rules as starting: completion waiting decides whether the task waits, deferrable mode only picks how it waits, and the triggerer polls with the task's region, SSL verification and botocore settings.
vincbeck
approved these changes
Oct 19, 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.
Add
EmrServerlessStopSessionOperator, which terminates an EMR Serverless interactive(Spark Connect) session and can wait until it reaches
TERMINATED.Why:
terminated or hit their idle timeout, so Dags need an explicit way to end a session
once their work is done.
Changes:
TerminateSessionboto3 API directly, after the samebotocore >= 1.43.0runtime check the other session operators use, so the provider'sdependency floor is unchanged.
EmrServerlessStopSessionTriggerand theserverless_session_terminatedwaiter supportsynchronous and deferrable waiting. As in
EmrServerlessStartSessionOperator,wait_for_completiondecides whether the task waits anddeferrableonly picks how,and the trigger polls with the task's region, SSL verification and botocore settings.
This completes the interactive session lifecycle started in #70763 (start) and #70766
(get endpoint). It replaces #70768, which the stale bot closed before it was reviewed.
Was generative AI tooling used to co-author this PR?
Generated-by: Kiro (Claude Opus 5.5) following the guidelines