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 2018/07/10 12:45:00 UTC
[jira] [Resolved] (FLINK-8863) Add user-defined function support in
SQL Client
[ https://issues.apache.org/jira/browse/FLINK-8863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timo Walther resolved FLINK-8863.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Fixed in 1.6.0: 8014dade4ba844786afa85fd517d6aba807dbc81 & abfdc1a2d649029d9f8a22c8d4880dc5068149c8
> Add user-defined function support in SQL Client
> -----------------------------------------------
>
> Key: FLINK-8863
> URL: https://issues.apache.org/jira/browse/FLINK-8863
> Project: Flink
> Issue Type: Sub-task
> Components: Table API & SQL
> Reporter: Timo Walther
> Assignee: Xingcan Cui
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
>
> This issue is a subtask of part two "Full Embedded SQL Client" of the implementation plan mentioned in [FLIP-24|https://cwiki.apache.org/confluence/display/FLINK/FLIP-24+-+SQL+Client].
> It should be possible to declare user-defined functions in the SQL client. For now, we limit the registration to classes that implement {{ScalarFunction}}, {{TableFunction}}, {{AggregateFunction}}. Functions that are implemented in SQL are not part of this issue.
> I would suggest to introduce a {{functions}} top-level property. The declaration could look similar to:
> {code}
> functions:
> - name: testFunction
> from: class <-- optional, default: class
> class: org.my.MyScalarFunction
> constructor: <-- optional, needed for certain types of functions
> - 42.0
> - class: org.my.Class <-- possibility to create objects via properties
> constructor:
> - 1
> - true
> - false
> - "whatever"
> - type: INT
> value: 1
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)