-
Notifications
You must be signed in to change notification settings - Fork 707
feat(udf): allow to ignore "language" in create function statements #10608
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
Signed-off-by: Runji Wang <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #10608 +/- ##
=======================================
Coverage 70.24% 70.24%
=======================================
Files 1274 1274
Lines 219182 219174 -8
=======================================
- Hits 153972 153967 -5
+ Misses 65210 65207 -3
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 6 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
What about something like language external?
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.
I'm considering is USING LINK enough to distinguish external function with e.g., SQL UDF, WASM UDF. And specifying the type explicitly might be better.
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.
I think language external can be inferred from using link. 🤔
As SQL UDF and WASM UDF will be executed inside kernel, they are not likely to have using links.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Currently users are required to specify the
languagein create function statements. But actually it is unnecessary in external function approach. So this PR makes thelanguagean optional field. If specified, it will be ignored for compatibility.Checklist
I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934)../risedev check(or alias,./risedev c)Documentation
Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.
Release note
The
languageparameter is no longer required in create function statements.