flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "xueyu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-11065) Migrate flink-table runtime classes
Date Fri, 07 Dec 2018 03:52:00 GMT

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

xueyu commented on FLINK-11065:

hi, [~hequn8128], I totally agree with you. Last time when I port UDF functions the PR has
a couple of issues.. so this time I would like to pick smaller \*Function.scala and \*Selector(Collector).scala
which have less codes than \*Runner. This way it may be easier to keep code quality than \*Runner.

Thank you very much, [~hequn8128][~twalthr] I will create \*Selector(Collector) and \*Function
two issues

> Migrate flink-table runtime classes
> -----------------------------------
>                 Key: FLINK-11065
>                 URL: https://issues.apache.org/jira/browse/FLINK-11065
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table API &amp; SQL
>            Reporter: Timo Walther
>            Priority: Major
> This issue covers the third step of the migration plan mentioned in [FLIP-28|https://cwiki.apache.org/confluence/display/FLINK/FLIP-28%3A+Long-term+goal+of+making+flink-table+Scala-free].
> All runtime classes have little dependencies to other classes.
> This issue tracks efforts of porting runtime classes.

This message was sent by Atlassian JIRA

View raw message