[SPARK-56245][PS] Fix DataFrame.eval inplace assignment on pandas 3#55041
Closed
ueshin wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-56245][PS] Fix DataFrame.eval inplace assignment on pandas 3#55041ueshin wants to merge 1 commit intoapache:masterfrom
ueshin wants to merge 1 commit intoapache:masterfrom
Conversation
Member
Author
HyukjinKwon
approved these changes
Mar 26, 2026
Member
|
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
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 updates pandas-on-Spark
DataFrame.evalto make a writable pandas copy before callingpdf.eval(..., inplace=True)on pandas 3.Why are the changes needed?
With pandas 3, the pandas batch frame used by pandas-on-Spark can be read-only. In that case, inplace expressions such as
psdf.eval("A = B + C", inplace=True)can fail with:Copying the batch only for the pandas 3 inplace path keeps the fix minimal and preserves the existing behavior for non-inplace
eval.Does this PR introduce any user-facing change?
No.
How was this patch tested?
The existing tests should pass.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Codex (GPT-5)