-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[feature](function) support variadic template type in SQL function #17985
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
Conversation
|
run buildall |
|
TeamCity pipeline, clickbench performance test result: |
|
run buildall |
|
run buildall |
cambyzju
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
|
run p0 |
…pache#17985) Inspired by c++ function `std::vector::emplace_back()`, we can use variadic template for this issue. e.g. ``` [['struct'], 'STRUCT<TYPES>', ['TYPES'], 'ALWAYS_NOT_NULLABLE', ['TYPES...']] ``` `...TYPES` in template_types defines a variadic template `TYPE`. Then the variadic template will be expanded to multiple normal templates based on actual input arguments at runtime in FE. But make sure `TYPES...` is placed on the last position in all template type arguments. BTW, the origin template function logic is not affected.
Proposed changes
In pr #17344, we already support template type in SQL function.
e.g.
Then it raises a new issue, as some functions require variable length template types.
e.g.
Inspired by c++ function
std::vector::emplace_back(), we can use variadic template for this issue.e.g.
...TYPESin template_types defines a variadic templateTYPE. Then the variadic template will be expanded to multiple normal templates based on actual input arguments at runtime in FE.But make sure
TYPES...is placed on the last position in all template type arguments.BTW, the origin template function logic is not affected.
Problem summary
Describe your changes.
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...