[SPARK-58465][PS] Use native expressions for NumPy reciprocal ufunc - #57668
Draft
zhengruifeng wants to merge 11 commits into
Draft
[SPARK-58465][PS] Use native expressions for NumPy reciprocal ufunc#57668zhengruifeng wants to merge 11 commits into
zhengruifeng wants to merge 11 commits into
Conversation
zhengruifeng
marked this pull request as draft
July 31, 2026 09:59
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?
Replace the scalar pandas UDF mapping for NumPy reciprocal on pandas-on-Spark objects with native Spark SQL expressions.
The expression uses typeof to distinguish Boolean, integral, and floating-point inputs. It preserves NumPy integer reciprocal behavior, including integer-zero overflow, as well as floating-point NaN, infinity, and signed-zero behavior. Add parity coverage for all of these cases.
Why are the changes needed?
The mapping can be evaluated with native Spark SQL expressions, avoiding the Python worker boundary while retaining NumPy-compatible results.
Does this PR introduce any user-facing change?
No. It preserves the existing NumPy-compatible result values and double output type.
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Codex (GPT-5)