[
https://issues.apache.org/jira/browse/FLINK-13741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bowen Li updated FLINK-13741:
-----------------------------
Summary: "SHOW FUNCTIONS" should include Flink built-in functions' names
(was: FunctionCatalog.getUserDefinedFunctions() should include Flink built-in
functions' names)
> "SHOW FUNCTIONS" should include Flink built-in functions' names
> ---------------------------------------------------------------
>
> Key: FLINK-13741
> URL: https://issues.apache.org/jira/browse/FLINK-13741
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Affects Versions: 1.9.0
> Reporter: Bowen Li
> Assignee: Bowen Li
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> FunctionCatalog.getUserDefinedFunctions() only returns catalog functions and
> FunctionDefinitions registered in memory, but does not include Flink built-in
> functions' names. It means currently if users call
> {{tEnv.listUserDefinedFunctions()}} in Table API or {{show functions;}} thru
> SQL, they would not be able to see Flink's built-in functions.
> AFAIK, it's standard for "SHOW FUNCTIONS;" to show all available functions
> for use in queries in SQL systems like Hive, Presto, Teradata, etc, thus it
> includes built-in functions naturally. Besides,
> {{FunctionCatalog.lookupFunction(name)}} resolves calls to built-in
> functions, it's not feeling right to not displaying functions but can
> successfully resolve to them.
> Thus, I propose {{FunctionCatalog.getUserDefinedFunctions()}} should be fixed
> to include Flink built-in functions' names.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
