flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabian Hueske (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-6457) Clean up ScalarFunction and TableFunction interface
Date Fri, 14 Jul 2017 10:08:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087133#comment-16087133

Fabian Hueske commented on FLINK-6457:

I propose to close this issue and PR [#3880|https://github.com/apache/flink/pull/3880] in
favor of FLINK-7193.

What do you think [~RuidongLi], [~shaoxuan] and [~jark]?

> Clean up ScalarFunction and TableFunction interface
> ---------------------------------------------------
>                 Key: FLINK-6457
>                 URL: https://issues.apache.org/jira/browse/FLINK-6457
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API & SQL
>            Reporter: Ruidong Li
>            Assignee: Ruidong Li
> Motivation:
> Some methods in ScalarFunction and TableFunction are unnecessary, e.g toString() and
getResultType in ScalarFunction
> this issue intend to clear the interface.
> Goal:
>  only methods related to `Collector` will remain in TableFunction interface, and ScalarFunction
interface shall have no methods , user can choose whether to implement the `getResultType`
method, which will be called by reflection, and the Flink document will have instructions
for user.
> Future:
> There should be some Annotations for user to implement methods like `@Eval` for eval
method, it be will in the next issue

This message was sent by Atlassian JIRA

View raw message