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 2017/04/21 12:02:04 UTC

[jira] [Commented] (FLINK-6355) TableEnvironment support register TableFunction

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

Fabian Hueske commented on FLINK-6355:
--------------------------------------

Can you explain the problem in more detail? 
{{java.BatchTableEnvironment}}, {{java.StreamTableEnvironment}}, {{scala.BatchTableEnvironment}} and {{scala.StreamTableEnvironment}} have dedicated methods to register TableFunctions.
If I remember correctly, the reason why this is split is due to incompatibilities of Java and Scala.

If I understood you correctly, you'd like to remove those methods and add one method to {{TableEnvironment}}, right? What would be the implications from a Java/Scala user point of view?

Thanks, Fabian

> TableEnvironment support register TableFunction
> -----------------------------------------------
>
>                 Key: FLINK-6355
>                 URL: https://issues.apache.org/jira/browse/FLINK-6355
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API & SQL
>            Reporter: Kaibo Zhou
>            Assignee: Kaibo Zhou
>
> Currently TableEnvironment only supports register ScalarFunction, it is necessary to support register TableFunction which is written in Java.
> The motivation is to eliminate most differences between batch and stream execution environment, and use TableEnvironment only to write programs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)