[SPARK-55665][PYTHON] Unify how workers establish connection with the executor#54458
Closed
gaogaotiantian wants to merge 2 commits intoapache:masterfrom
Closed
[SPARK-55665][PYTHON] Unify how workers establish connection with the executor#54458gaogaotiantian wants to merge 2 commits intoapache:masterfrom
gaogaotiantian wants to merge 2 commits intoapache:masterfrom
Conversation
HyukjinKwon
approved these changes
Feb 24, 2026
zhengruifeng
approved these changes
Feb 26, 2026
Contributor
|
merged to master |
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.
What changes were proposed in this pull request?
Unify all the sock file connections from different worker files together. And guarantee an explicit flush and close for the sock file.
Why are the changes needed?
We now copy/paste this piece of code all over our code base and it introduces a few issues.
data_source_pushdown_filters.pyforgets to write pid back but we never test it.It's best to just organize the code at a single place.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Locally
test_python_datasourcepassed, the rest is on CI.Was this patch authored or co-authored using generative AI tooling?
Yes, Cursor(claude-4.6-opus-high).