You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2019/01/29 12:58:00 UTC
[jira] [Closed] (FLINK-11066) Migrate main Table API classes to
flink-table-api-base
[ https://issues.apache.org/jira/browse/FLINK-11066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timo Walther closed FLINK-11066.
--------------------------------
Resolution: Duplicate
As FLIP-32 replaces FLIP-28 and the number of JIRA issues is already quite complex. I will close this issue. See FLINK-11448 for similar efforts.
> 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 & SQL
> Reporter: Timo Walther
> 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
(v7.6.3#76005)