[FLINK-11064] Setup a new flink-table module structure

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.8.0
• Component/s: Table SQL / API
• Labels: pull-request-available
• Release Note: Users that had a `flink-table` dependency before need to update their dependencies to `flink-table-planner` and for Java `flink-table-api-java-bridge` or for Scala `flink-table-api-scala-bridge`.
• Assignee: Timo Walther
• Reporter: Timo Walther
• Created: 04/Dec/18 10:35
• Updated: 31/Jan/19 09:35
• Resolved: 31/Jan/19 09:35

Description

This issue covers the first step of the implementation plan mentioned in FLIP-32.

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.

Issue Links

• links to: GitHub Pull Request #7409
• links to: GitHub Pull Request #7587