Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
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`.
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.