[GH-2565] Fix NULL handling for various aggregation functions in SedonaSpark#2563
Merged
jiayuasu merged 2 commits intoapache:masterfrom Dec 17, 2025
Merged
Conversation
fbf1027 to
cfb6c9d
Compare
Member
Author
|
The Python build extension failure is probably caused by the newly released PySpark 4.1.0 not playing well with Windows. See apache/spark#50466 |
jiayuasu
approved these changes
Dec 17, 2025
Kontinuation
added a commit
to Kontinuation/sedona
that referenced
this pull request
Jan 21, 2026
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.
Did you read the Contributor Guide?
Is this PR related to a ticket?
[GH-2565] my subject. Closes Aggregation functions in SedonaSpark throw exception when processingNULLvalues #2565What changes were proposed in this PR?
This PR refactors several spatial aggregate functions to fix
NULLhandling. Impacted functions areHow was this patch tested?
Added new tests and tested locally using a standalone cluster to make sure that we are not damaging the serde in distributed environment.
Did this PR include necessary documentation updates?