[SPARK-59357][CONNECT][TEST] Improve Python client plan test coverage - #58643
Open
zhengruifeng wants to merge 2 commits into
Open
[SPARK-59357][CONNECT][TEST] Improve Python client plan test coverage#58643zhengruifeng wants to merge 2 commits into
zhengruifeng wants to merge 2 commits into
Conversation
zhengruifeng
changed the title
zhengruifeng
force-pushed
the
py-connect-plan-coverage-dev-6
branch
from
September 9, 2026 06:20
5f590d4 to
e8c02c3
Compare
zhengruifeng
changed the title
uros-b
approved these changes
Sep 9, 2026
uros-b
left a comment
uros-b
left a comment
Member
There was a problem hiding this comment.
There are some conflicts, but otherwise looks good!
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
2 participants
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?
This PR addresses SPARK-59357.
This PR expands the Python Spark Connect plan-only tests for DataFrame APIs. It adds protobuf plan assertions for:
toDFoperations;zipWithIndex,repartitionById, and deduplication within a watermark.It also updates the existing union alias coverage to exercise
unionAlldirectly.Why are the changes needed?
These DataFrame APIs previously lacked focused tests of the protobuf plans generated by the Python client. The additional plan-only coverage catches client-side serialization regressions without requiring a running Spark server.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
Generated-by: OpenAI Codex (GPT-5)