You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2018/03/15 10:34:00 UTC

[jira] [Closed] (FLINK-3497) Add SQL scalar functions to Table API

     [ https://issues.apache.org/jira/browse/FLINK-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fabian Hueske closed FLINK-3497.
--------------------------------
    Resolution: Fixed
      Assignee: Timo Walther

Closing. All sub issues have been resolved.

> Add SQL scalar functions to Table API
> -------------------------------------
>
>                 Key: FLINK-3497
>                 URL: https://issues.apache.org/jira/browse/FLINK-3497
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table API &amp; SQL
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>            Priority: Major
>
> In order to use the Table API as ETL tool and prepare for FLINK-2099, we need to add more scalar functions such as {{trim()}}, {{abs()}}, {{like()}}, etc.
> Calcite implements the most important functions. We can basically forward calls to Calcites built-in runtime functions. Some functions need special treatment because of Flink specifics.
> I would propose the following steps:
> - Implement TRIM, SUBSTRING as reference design
> - remaining string functions
> - math functions
> - Date/time functions
> - System functions
> - Case function
> - Array functions
> - other
> Each step includes implementation, test and documentation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)