[SPARK-58225][PYTHON] Delete unused TransformWithStateInPandasSerializer#57382
Open
Yicong-Huang wants to merge 1 commit into
Open
[SPARK-58225][PYTHON] Delete unused TransformWithStateInPandasSerializer#57382Yicong-Huang wants to merge 1 commit into
Yicong-Huang wants to merge 1 commit into
Conversation
HyukjinKwon
approved these changes
Jul 20, 2026
uros-b
approved these changes
Jul 21, 2026
uros-b
left a comment
uros-b
left a comment
Member
There was a problem hiding this comment.
Thank you @Yicong-Huang and @HyukjinKwon!
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
3 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?
Delete the unused
TransformWithStateInPandasSerializer. It became dead code after SPARK-58128 moved its logic intoread_udfs()and SPARK-58190 removed its only subclass.Why are the changes needed?
Dead-code cleanup. No remaining references.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests. No behavior change.
Was this patch authored or co-authored using generative AI tooling?
No.