[SPARK-55472][PS] Raise AttributeError from methods removed in pandas 3
#54249
Conversation
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
Member
Author
gaogaotiantian
approved these changes
Feb 10, 2026
HyukjinKwon
approved these changes
Feb 10, 2026
zhengruifeng
approved these changes
Feb 11, 2026
Contributor
|
merged to master |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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?
Raises
AttributeErrorfrom methods removed in pandas 3.DataFrame/Series:backfill,pad,first,last,swapaxesGroupBy:fillnaIndex:hold_integerWhy are the changes needed?
There are some methods removed in pandas 3, which should raise
AttributeErrorin pandas API on Spark, too.Does this PR introduce any user-facing change?
Yes, the methods removed in pandas 3 will raise
AttributeErrorwith pandas 3.How was this patch tested?
Updated the related tests.
Was this patch authored or co-authored using generative AI tooling?
No.