[
https://issues.apache.org/jira/browse/FLINK-15609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016596#comment-17016596
]
Jark Wu edited comment on FLINK-15609 at 1/16/20 6:43 AM:
----------------------------------------------------------
Should we mark a higher priority for this issue? AFAIK, it lead to the new
functions introduced by blink planner can't work (about 36 functions).
You can search "blink planner" in this page:
https://ci.apache.org/projects/flink/flink-docs-master/dev/table/functions/systemFunctions.html
was (Author: jark):
Should we mark a higher priority for this issue. AFAIK, it lead to the new
functions introduced by blink planner can't work (about 36 functions).
You can search "blink planner" in this page:
https://ci.apache.org/projects/flink/flink-docs-master/dev/table/functions/systemFunctions.html
> Add blink built-in functions from FlinkSqlOperatorTable to
> BuiltInFunctionDefinitions
> -------------------------------------------------------------------------------------
>
> Key: FLINK-15609
> URL: https://issues.apache.org/jira/browse/FLINK-15609
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API
> Reporter: Jingsong Lee
> Priority: Major
> Fix For: 1.10.0
>
>
> In FLINK-15595, CoreModule should contains all functions in
> FlinkSqlOperatorTable. Otherwise, resolution Order is chaotic. I think it is
> time to align blink built-in functions to BuiltInFunctionDefinitions.
> Impact to legacy planner: user can not use the function name directly that he
> define function with the same name of blink built-in function in catalog. I
> think it is reasonable, since he will migrate his job to blink planner.
> What do you think? [~twalthr] [~dwysakowicz]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
