-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-44422][CONNECT] Spark Connect fine grained interrupt #42009
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
juliuszsompolski
wants to merge
21
commits into
apache:master
from
juliuszsompolski:sc-fine-grained-cancel
Closed
Changes from 1 commit
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
16d126f
protos
juliuszsompolski 6d073cc
error class
juliuszsompolski 380a373
server side changes
juliuszsompolski 4d9ad53
clean after merge
juliuszsompolski 6095e6b
lint
juliuszsompolski 65e9cf5
fix error doc
juliuszsompolski ae6cbaf
fix after rebase
juliuszsompolski b213c00
INTERRUPT_TYPE_ID -> INTERRUPT_TYPE_OPERATION_ID
juliuszsompolski a297d45
scala client, without tests
juliuszsompolski e6bdcab
check returned operations id in interruptAll
juliuszsompolski 32126e7
interruptTag test
juliuszsompolski 2e32219
add to SparkListenerConnectOperationStarted
juliuszsompolski 608c792
interrupt operation test
juliuszsompolski 5112ccf
lint
juliuszsompolski 3655ebf
self review
juliuszsompolski 6024e24
null->_
juliuszsompolski 63f7a05
rename userDefinedTags to sparkSessionTags
juliuszsompolski 652091f
fix mima
juliuszsompolski 8198654
fix scala 2.13
juliuszsompolski e4047e3
regenerate python protos
juliuszsompolski b8a4ac7
make interruptedId be returned only once to deflake test
juliuszsompolski File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
lint
- Loading branch information
commit 5112ccfc48c7a2805773f0d15facb1e2f25c65a3
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible that we block on receiving this operationId from the server? When that happens we can only interrupt all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently getting the operationId is indeed a bit awkward, and adding tags interruptTag is a more convenient API to use.
This will still be improved in a followup PR for async and detachable API execution. Some preparation is here already - https://github.com/apache/spark/pull/42009/files#diff-3cad257dc0c15b4d091beebdfd42659f803193c23667425d8926b84113a2a312R288 operationId can also be passed in ExecutePlanRequest, so that the client already knows it from the start and doesn't need to take it from first response.
In my followup PR I also plan to add a response that would always be sent right at the beginning of the query, so that even if the client did not set the operationId, it can get it right away.