You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "TisonKun (JIRA)" <ji...@apache.org> on 2018/10/26 08:09:00 UTC

[jira] [Commented] (FLINK-10686) Introduce a flink-table-common module

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

TisonKun commented on FLINK-10686:
----------------------------------

I like this proposal and volunteer to be a reviewer. Go ahead!

Also I think table API might be further recommended approach for user to write their application. Thus refactor (including this) is welcome to me.

> Introduce a flink-table-common module
> -------------------------------------
>
>                 Key: FLINK-10686
>                 URL: https://issues.apache.org/jira/browse/FLINK-10686
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API &amp; SQL
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>            Priority: Major
>
> Because more and more table factories for connectors and formats are added and external catalog support is also on the horizon, {{flink-table}} becomes a dependency for many Flink modules. Since {{flink-table}} is implemented in Scala it requires other modules to be suffixes with Scala prefixes. However, as we have learned in the past, Scala code is hard to maintain which is why our long-term goal is to avoid Scala/Scala dependencies.
> Therefore we propose a new module {{flink-table-common}} that contains interfaces between {{flink-table}} and other modules. This module is implemented in Java and should contain minimal (or better no) external dependencies.



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