[
https://issues.apache.org/jira/browse/FLINK-24427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422979#comment-17422979
]
Erwan Loisant edited comment on FLINK-24427 at 9/30/21, 7:08 PM:
-----------------------------------------------------------------
I'm not sure what's the proposed solution here, I don't think hiding the
version would really make it possible to use code compiled for Scala 2.12 in
2.13.
So I guess either we cross-compile to multiple version (like it was done for
2.11 and 2.12 until now), or we migrate all the code to Java?
was (Author: eloisant):
I'm not sure what's the proposed solution here, I don't think hiding the
version would really make it possible to use code compiled for Scala 2.12 in
2.13.
So I guess either we cross-compile to multiple version (like it was done for
2.11 and 2.12 until now), or we migrate all the code to Java?
> Hide Scala in flink-table-planner from API
> ------------------------------------------
>
> Key: FLINK-24427
> URL: https://issues.apache.org/jira/browse/FLINK-24427
> Project: Flink
> Issue Type: Sub-task
> Components: API / Scala, Table SQL / API, Table SQL / Planner
> Reporter: Timo Walther
> Priority: Major
>
> 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.3.4#803005)
