Add support for lazy scalar function argument evaluation #17997
+397
−55
Conversation
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
github-actions
bot
added
logical-expr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Which issue does this PR close?
Rationale for this change
This PR provides an alternative mechanism for scalar UDFs to control argument evaluation besides rewriting to other constructs like
case.What changes are included in this PR?
ScalarUDF::invoke_with_deferred_argumentsScalarFunctionExprto use this mechanism when the function is declared to be short circuiting.nvl.Are these changes tested?
Covered by SQL logic tests
Are there any user-facing changes?
The new mechanism doesn't change anything. For
nvlspecifically, argument evaluation changes from eager to lazy.