[
https://issues.apache.org/jira/browse/FLINK-13414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17344365#comment-17344365
]
Zhenhao Li commented on FLINK-13414:
------------------------------------
[~Davidho] Supporting Scala is hard for a project like Flink. Scala was very
clear about its principles: we will keep making breaking changes (until Scala 3
hopefully). That means full Scala user support has to be all-in or nothing.
Confluent gave up on Kafka's native Scala API years ago. If I remember
correctly, the current Scala API if existing is just a wrapper of the Java API.
Keeping up with every major version of Scala is a lot of work. A well-founded
Scala shop like Databricks can't do it well.
Now the question is, can companies trust the backward compatible promise of
Scala 3 onwards?
If yes, moving to Scala 3 will be the last painful hard work.
If no, it is better for everyone to simply drop native Scala support.
I think the low-hanging fruit is to properly hide the Akka Scala 2.12
dependencies in the Java API jars of the Flink release, which allow eager Scala
users to use it with Scala 3. There is no need to touch the Scala API.
[~sewen]What's your take on this?
> Add support for Scala 2.13
> --------------------------
>
> Key: FLINK-13414
> URL: https://issues.apache.org/jira/browse/FLINK-13414
> Project: Flink
> Issue Type: New Feature
> Components: API / Scala
> Reporter: Chaoran Yu
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
