[SPARK-51757] Fix LEAD/LAG Function Offset Exceeds Partition Size #50552
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?
The current implementation of the
prepare
inOffsetWindowFunctionFrameBase
:The current implementation of the
write
inOffsetWindowFunctionFrameBase
:These implementations caused the
LEAD' and
LAGfunctions to have
NullPointerExceptionwhen the default value is not
Literal` and the range of the default value exceeds the partition size.This pr removes the default values in
prepare
and sets the default values inwrite
.Why are the changes needed?
Fix
LEAD
andLAG
causes NullPointerException in the window function (SPARK-51757)Does this PR introduce any user-facing change?
No
How was this patch tested?
Add test method in test("SPARK-51757: lead/lag column as default when offset exceeds partition") in org.apache.spark.sql.DataFrameWindowFramesSuite
Was this patch authored or co-authored using generative AI tooling?
No.