[
https://issues.apache.org/jira/browse/FLINK-24427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Guardiani closed FLINK-24427.
---------------------------------------
Fix Version/s: 1.15.0
Release Note:
The new module flink-table-planner-loader replaces flink-table-planner_2.12 and
avoids the need for a Scala suffix. It is included in the Flink distribution
under /lib. For backwards compatibility, users can still swap it with
flink-table-planner_2.12 located in /opt. As a consequence, flink-table-uber
has been split into flink-table-api-java-uber, flink-table-planner(-loader),
and table-runtime. flink-sql-client has no Scala suffix anymore.
It is recommended to let new projects depend on flink-table-planner-loader
(without Scala suffix) in provided scope.
Note that the distribution does not include the Scala API by default. Scala
users need to explicitly add a dependency to flink-table-api-scala or
flink-table-api-scala-bridge.
Resolution: Fixed
> Hide Scala in flink-table-planner from API
> ------------------------------------------
>
> Key: FLINK-24427
> URL: https://issues.apache.org/jira/browse/FLINK-24427
> Project: Flink
> Issue Type: Technical Debt
> Components: API / Scala, Table SQL / API, Table SQL / Planner
> Reporter: Timo Walther
> Assignee: Francesco Guardiani
> Priority: Major
> Fix For: 1.15.0
>
>
> FLIP-32 has decoupled the planner from the API. However, the planner code
> base is still the largest Scala code base we have in Flink that we cannot
> port to Java easily.
> In order to allow arbitrary Scala versions in the user API, we suggest to
> hide the Scala version of the planner from the Scala version of the API. The
> API is mostly developed in Java and contains only a couple of classes
> implemented in Scala. Those should be easier to maintain for various Scala
> versions. The planner is already discovered via Java SPI.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
