flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vinoyang (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (FLINK-11066) Migrate main Table API classes to flink-table-api-base
Date Wed, 05 Dec 2018 01:16:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-11066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

vinoyang reassigned FLINK-11066:

    Assignee: vinoyang

> Migrate main Table API classes to flink-table-api-base
> ------------------------------------------------------
>                 Key: FLINK-11066
>                 URL: https://issues.apache.org/jira/browse/FLINK-11066
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table API &amp; SQL
>            Reporter: Timo Walther
>            Assignee: vinoyang
>            Priority: Major
> This issue covers the forth 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].
> The most important API classes such as TableEnvironments and Table are exposing a lot
of protected methods in Java. Migrating those classes makes the API clean and the implementation
ready for a major refactoring for the new catalog support. We can also think about a separation
of interface and implementation; e.g. {{Table}} & {{TableImpl}}. However, the current
API design makes this difficult as we are using constructors of interfaces {{new Table(...)}}.
> This issue tracks efforts of porting API classes.

This message was sent by Atlassian JIRA

View raw message