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/31 09:11:00 UTC

[jira] [Closed] (FLINK-11064) Setup a new flink-table module structure

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

Timo Walther closed FLINK-11064.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.8.0

Fixed in 1.8.0: 0ab1549f52f1f544e8492757c6b0d562bf50a061

> Setup a new flink-table module structure
> ----------------------------------------
>
>                 Key: FLINK-11064
>                 URL: https://issues.apache.org/jira/browse/FLINK-11064
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table API &amp; SQL
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.8.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> This issue covers the first step of the implementation plan mentioned in [FLIP-32|https://cwiki.apache.org/confluence/display/FLINK/FLIP-32%3A+Restructure+flink-table+for+future+contributions].
> Move all files to their corresponding modules as they are. No migration happens at this stage. Modules might contain both Scala and Java classes. Classes that should be placed in `flink-table-common` or `flink-table-api-*` but are in Scala so far remain in `flink-table-planner` for now.



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