Introduce Async User Defined Functions #14837
Draft
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
I have been working with @alamb to implement the functional for the async UDF.
It introduces the following trait:
It allows the user to implement the UDF for invoking some external remote function in the query.
Given an async udf
async_equal
, the plan would look like:To reduce the number of invoking the async function,
CoalesceAsyncExecInput
rule is used for coalescing the input batch ofAsyncFuncExec
.See the details usages in the example.
What changes are included in this PR?
Remaining Work
Maybe implement in the follow-up PR
Are these changes tested?
Are there any user-facing changes?