[
https://issues.apache.org/jira/browse/FLINK-15609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323121#comment-17323121
]
Flink Jira Bot commented on FLINK-15609:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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
> Assignee: Danny Chen
> Priority: Major
> Labels: stale-assigned
>
> 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)
