[SPARK-58548][PS] Use native Spark function for NumPy heaviside - #57749
Open
zhengruifeng wants to merge 3 commits into
Open
[SPARK-58548][PS] Use native Spark function for NumPy heaviside#57749zhengruifeng wants to merge 3 commits into
zhengruifeng wants to merge 3 commits into
Conversation
uros-b
approved these changes
Aug 4, 2026
Member
|
Thank you @zhengruifeng, just please resolve conflicts |
zhengruifeng
force-pushed
the
pandas-native-heaviside-dev2
branch
from
August 4, 2026 13:35
52f288e to
c1aaa0c
Compare
zhengruifeng
force-pushed
the
pandas-native-heaviside-dev2
branch
from
August 5, 2026 01:22
5af3a3d to
df13ed2
Compare
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 replaces the pandas UDF implementation of
np.heavisidein pandas API on Spark with a native Sparkwhenexpression. It returns0.0for negative values, the second argument at either signed zero, and1.0for positive values; null and NaN first arguments propagate.The new test covers integral inputs, signed zero, NaN, infinities, and NaN as the second argument at zero.
Why are the changes needed?
Using native Spark expressions avoids pandas UDF and Arrow overhead while preserving NumPy
heavisidesemantics.Does this PR introduce any user-facing change?
No.
How was this patch tested?
NumPyCompatTests.test_np_heaviside.ruff check python/pyspark/pandas/numpy_compat.py python/pyspark/pandas/tests/test_numpy_compat.pyruff format --check python/pyspark/pandas/numpy_compat.py python/pyspark/pandas/tests/test_numpy_compat.pypython -m unittest pyspark.pandas.tests.test_numpy_compat.NumPyCompatTests.test_np_heavisideWas this patch authored or co-authored using generative AI tooling?
Generated-by: Codex GPT-5