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?
Closes #12144.
Rationale for this change
This PR implements
SHOW FUNCTIONS
to list the available functions during runtime. Instead of listing the function name only (like Apache Spark), I think it's better to provide more information like what Snowflake did.To provide the required information, I also added some columns to
information_schema.routines
andinformation_schema.parameters
.Syntax
Sample Output
The Output Schema
function_name
return_type
parameters
: The name of parameters (ordered by the ordinal position)parameter_types
: The type of parameters (ordered by the ordinal position)description
: The description of the function (the description defined in the document)syntax_example
: The syntax_example of the function (the syntax_example defined in the document)What changes are included in this PR?
SHOW FUNCTIONS
.syntax_example
field toinformation_schema.routines
.rid
field toinformation_schema.parameters
.rid
(short forroutine id
) is used to differentiate parameters from different signatures (it serves as the group-by key when generating theSHOW FUNCTIONS
query). For example, the following signatures have differentrid
values:datetrunc(Utf8, Timestamp(Microsecond, Some("+TZ"))) -> Timestamp(Microsecond, Some("+TZ"))
datetrunc(Utf8View, Timestamp(Nanosecond, None)) -> Timestamp(Nanosecond, None)
Are these changes tested?
yes, tested by sqllogictests
Are there any user-facing changes?
New SQL syntax.