You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (Jira)" <ji...@apache.org> on 2020/05/26 09:07:00 UTC
[jira] [Commented] (FLINK-15609) Add blink built-in functions from
FlinkSqlOperatorTable to BuiltInFunctionDefinitions
[ https://issues.apache.org/jira/browse/FLINK-15609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116551#comment-17116551 ]
Timo Walther commented on FLINK-15609:
--------------------------------------
So can we downgrade this issue to just Major?
> 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: Critical
> Fix For: 1.11.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)