[
https://issues.apache.org/jira/browse/FLINK-28071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555445#comment-17555445
]
LuNing Wang commented on FLINK-28071:
-------------------------------------
[~twalthr] I only support existing built-in functions no more new functions in
this issue. Should I not use the new stack, or in the future we create a new
issue to refactor all built-in functions to the new stack?
Like this PR [https://github.com/apache/flink/pull/19988] . If I use the new
stack, I will delete the `StringCallGen#generateAscii` and add an
`AsciiFunction` like IfNullFunction in
https://issues.apache.org/jira/browse/FLINK-20522
IMO, if we change `StringCallGen#generateAscii`, we can create a new issue.
> Support missing built-in functions in Table API
> -----------------------------------------------
>
> Key: FLINK-28071
> URL: https://issues.apache.org/jira/browse/FLINK-28071
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API
> Reporter: Dian Fu
> Assignee: LuNing Wang
> Priority: Major
> Fix For: 1.16.0
>
>
> There are many built-in functions are not supported. See
> https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/functions/systemfunctions/
> for more details. There are two columns for each built-in function: *SQL
> Function* and *Table Function*, if a function is not supported in *Table
> API*, the *Table Function* column is documented as *N/A*. We need to evaluate
> each of these functions to ensure that they could be used in both SQL and
> Table API.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
