HIVE-24908: Adding Respect/Ignore nulls as a UDAF parameter is ambiguous #2091
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?
respectNulls
boolean property toGenericUDAFParameterInfo
.WindowFunctionDescription
which show whether the function supports handling null treatment settings.supportNullTreatment
property is not set explicitly the UDAF does not support null treatment and the compiler throwsSemanticException
if specified.supportNullTreatment
property is set to true but the function call does not specify null treatment the default null treatment is used:RESPECT NULLS
Why are the changes needed?
This patch is a follow-up of #2060. See jira for details.
Does this PR introduce any user-facing change?
Yes. When calling
lead
orlag
functions by specifyingRESPECT/IGNORE NULLS
RESPECT/IGNORE NULLS
are not passed as default value parameter:NULL
is returned if rows has no corresponding following/preceding rowsRESPECT/IGNORE NULLS
are not passed as default value parameter: no Exception is thrownHow was this patch tested?