-
Notifications
You must be signed in to change notification settings - Fork 590
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
refactor(test): refactor sql udf test #14941
Conversation
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.
Just some nits not strictly related with this reorg
e2e_test/udf/sql_udf.slt
Outdated
# create materialized view foo_mv as select fib(100); | ||
|
||
# Calling a non-existence function | ||
statement error failed to conduct semantic check, please see if you are calling non-existence functions |
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.
non-existent
e2e_test/udf/sql_udf.slt
Outdated
@@ -1,325 +1,346 @@ | |||
statement ok | |||
SET RW_IMPLICIT_FLUSH TO true; | |||
|
|||
############################################# | |||
# Basic tests for anonymous / named sql udf # |
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 anonymous function means function without a name. usually a closure. Better to just call them functions with named parameters.
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 unnamed / named sql udf is a good choice then. 😄
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.
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.
Then let's just stick with "sql udf with [named / unnamed] parameters", which should be precise and clear in most contexts.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
As titled, refactor the current sql udf test suite to five sections, to improve the readability & future maintainability.
See the updated test for details.
Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
Just a reminder of the naming convention of sql udf, now we will stick with: SQL udf with [unnamed / named] parameters, instead of the original [anonymous / named] sql udf. The documentation may be updated accordingly.
Reference: #14941 (comment).