-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-44509][CONNECT][FOLLOW-UP] Add inheritable support in new job cancellation API #42149
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
Conversation
| :class:`threading.Thread` but correctly inherits the inheritable properties specific | ||
| to JVM thread such as ``InheritableThreadLocal``. | ||
| Also, note that pinned thread mode does not close the connection from Python |
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.
This is already fixed in Py4J, py4j/py4j#471
|
cc @zhengruifeng and @WeichenXu123 I need your look here. |
|
LGTM, but I think we need @WeichenXu123 's approval for this PR |
WeichenXu123
left a comment
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.
LGTM!
b03109f to
391ce44
Compare
dongjoon-hyun
left a comment
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.
+1, LGTM (Pending CIs)
|
All tests passed. The failed test is pip packaging test that happens after running all unittests. I will fix them separately at #42159. Merged to master and branch-3.5. |
What changes were proposed in this pull request?
This PR is a kind of a followup of #42120. This addresses my own comment at #42120 (comment) by adding the support of
InheritableThreadwith Spark Connect.Why are the changes needed?
In order to allow the thread local hierarchy supported in Scala side.
Does this PR introduce any user-facing change?
The main PR is not released out yet so it doesn't have user-facing change.
How was this patch tested?
Unittests were added.