-
Notifications
You must be signed in to change notification settings - Fork 3.5k
[feat](udf) support "prefer_udf_over_builtin" session variable #51195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
run buildall |
TPC-H: Total hot run time: 34700 ms
|
TPC-DS: Total hot run time: 193272 ms
|
ClickBench: Total hot run time: 28.69 s
|
run buildall |
TPC-H: Total hot run time: 33903 ms
|
TPC-DS: Total hot run time: 186105 ms
|
ClickBench: Total hot run time: 29.11 s
|
morrySnow
approved these changes
May 27, 2025
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
hubgeter
approved these changes
May 27, 2025
wuwenchi
approved these changes
May 27, 2025
github-actions bot
pushed a commit
that referenced
this pull request
May 27, 2025
### What problem does this PR solve? Problem Summary: Add a new session variable `prefer_udf_over_builtin`. Default is false. If set to true, the planner will first find function from UDF, then builtin function. This feature is useful when user migration from other system to Doris, but function behavior with same signature between 2 system are different. In this case, user can create a UDF with same signature to override the builtin function, so that user don't need to change their SQL.
koarz
pushed a commit
to koarz/doris
that referenced
this pull request
Jun 4, 2025
…e#51195) ### What problem does this PR solve? Problem Summary: Add a new session variable `prefer_udf_over_builtin`. Default is false. If set to true, the planner will first find function from UDF, then builtin function. This feature is useful when user migration from other system to Doris, but function behavior with same signature between 2 system are different. In this case, user can create a UDF with same signature to override the builtin function, so that user don't need to change their SQL.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
Indicates a PR has been approved by one committer.
dev/3.0.7-merged
reviewed
usercase
Important user case type label
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 problem does this PR solve?
Problem Summary:
Add a new session variable
prefer_udf_over_builtin
. Default is false.If set to true, the planner will first find function from UDF, then builtin function.
This feature is useful when user migration from other system to Doris, but function behavior
with same signature betweem 2 system are different.
In this case, user can create a UDF with same signature to override the builtin function,
so that user don't need to change their SQL.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)