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/03 16:25:00 UTC

[jira] [Updated] (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 updated FLINK-11064:
---------------------------------
    Description: 
This issue covers the first 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].

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` but are in Scala so far remain in `flink-table-api-planner` for now.

  was:
This issue covers the first 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].

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-spi` but are in Scala so far remain in `flink-table-api-base` for now.


> 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
>
> This issue covers the first 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].
> 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` but are in Scala so far remain in `flink-table-api-planner` for now.



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