[SEDONA-348] Implemented null-tolerant variants of inferred functions #952
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 JIRA ticket?
[SEDONA-XXX] my subject
.What changes were proposed in this PR?
Functions such as
ST_MakePoint
need to accept null as ordinates. For example, we can useST_MakePoint(x, y, null, m)
to construct a point object with M ordinate. This requires theInferredExpression
to support null-tolerant functions.This patch introduces a family of
nullTolerantInferredFunction
functions for wrapping null-tolerant functions as spark catalyst expressions. For example,makePoint
can be wrapped in this way:We won't check null values for function arguments when evaluating
ST_MakePoint
and it is up to the wrapped function (makePoint
in this case) to handle null values correctly.How was this patch tested?
We've cherry-picked this patch on top of #950 and verified that it works as expected.
It will be covered by more null-tolerant functions we'll implement in the future.
Did this PR include necessary documentation updates?