Hi Salva, Like Robert said, I don't expect that we will be able to drop support for Scala 2.12 anytime soon. I do think that we should have a discussion in the Flink community about providing Scala APIs. My opinion is that we are probably better off to deprecate the current Scala APIs (keeping it internal as we still have a big piece of Scala internally) and only offer Java APIs. The Flink community lacks real Scala maintainers. I think Seth's blog is pretty spot-on on this too [1].
Best regards, Martijn Visser https://twitter.com/MartijnVisser82 https://github.com/MartijnVisser [1] https://flink.apache.org/2022/02/22/scala-free.html On Mon, 9 May 2022 at 12:24, Robert Metzger <metrob...@gmail.com> wrote: > Hi Salva, > my somewhat wild guess (because I'm not very involved with the Scala > development on Flink): I would stick with option 1 for now. It should be > easier now for the Flink community to support Scala versions past 2.12 > (because we don't need to worry about scala 2.12+ support for Flink's > internal dependencies such as akka). > An argument against supporting newer Scala versions is that I'm not aware > of anybody currently working on Flink with Scala in general. > > On Fri, May 6, 2022 at 6:37 PM Salva Alcántara <salcantara...@gmail.com> > wrote: > >> I've always used Scala in the context of Flink. Now that Flink 1.15 has >> become Scala-free, I wonder what is the best (most practical) route for me >> moving forward. These are my options: >> >> 1. Keep using Scala 2.12 for the years to come (and upgrade to newer >> versions when the community has come up with something). How long is Flink >> expected to support Scala 2.12? >> >> 2. Upgrade to Scala 2.13 or Scala 3 and use the Java API directly >> (without any Scala-specific wrapper/API). How problematic will that be, >> especially regarding type information & scala-specific serializers? I hate >> those "returns" (type hints) in the Java API... >> >> 3. Switch to Java, at least for the time being... >> >> To be clear, I have a strong preference for Scala over Java, but I'm >> trying to look at the "grand scheme of things" here, and be pragmatic. I >> guess I'm not alone here, and that many people are indeed evaluating the >> same pros & cons. Any feedback will be much appreciated. >> >> Thanks in advance! >> >
