Sorry, I forgot the link of the repo: https://github.com/salvalcantara/flink-scala
Regards, Salva On Wed, May 11, 2022 at 9:32 AM Salva Alcántara <[email protected]> wrote: > Thanks Martijn, my conclusion so far is that Java is a safe bet. > > In the meantime, a friend and I have spent some time trying to make > `flink-scala` work with Flink 1.15 and Scala 2.13. We partly followed the > discussions in [1] (FLINK-13414) to fix all the compilations errors. Note > that this is just a few-hour (very naive) experiment, but might be useful > as a starting point. > > Thanks, > > Salva > > On Wed, May 11, 2022 at 9:10 AM Martijn Visser <[email protected]> > wrote: > >> Hi Matthias, >> >> Given the current state of Scala support in the Flink community (there is >> a major lack in Scala maintainers), it is my personal opinion that we >> should consider deprecating the current Scala APIs and replace those with >> new Scala APIs, which are 'just' wrappers for the Java API. This definitely >> needs a FLIP and a discussion, where I can explain the situation more. >> There's nothing concrete for this yet though. There have been some >> discussions on this topic going on in the ticket for adding Scala 2.13 >> support [1] >> >> Best regards, >> >> Martijn >> >> [1] >> https://issues.apache.org/jira/browse/FLINK-13414?focusedCommentId=17344555&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17344555 >> >> On Tue, 10 May 2022 at 16:16, Schwalbe Matthias < >> [email protected]> wrote: >> >>> … just for my understanding >>> >>> >>> >>> From the announcements I only got that scala remains only a dependency >>> in the JARs that relate to the Scala API. >>> >>> I never read about plans to drop the Scala API altogether … is that the >>> case?? >>> >>> That would be very unfortunate … >>> >>> >>> >>> What is the state of the affair? >>> >>> >>> >>> Best regards >>> >>> >>> >>> Thias >>> >>> >>> >>> >>> >>> >>> >>> *From:* Martijn Visser <[email protected]> >>> *Sent:* Monday, May 9, 2022 2:38 PM >>> *To:* Robert Metzger <[email protected]> >>> *Cc:* Salva Alcántara <[email protected]>; user < >>> [email protected]> >>> *Subject:* Re: Practical guidance with Scala and Flink >= 1.15 >>> >>> >>> >>> ⚠*EXTERNAL MESSAGE – **CAUTION: Think Before You Click *⚠ >>> >>> >>> >>> 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 <[email protected]> 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 <[email protected]> >>> 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! >>> >>> Diese Nachricht ist ausschliesslich für den Adressaten bestimmt und >>> beinhaltet unter Umständen vertrauliche Mitteilungen. Da die >>> Vertraulichkeit von e-Mail-Nachrichten nicht gewährleistet werden kann, >>> übernehmen wir keine Haftung für die Gewährung der Vertraulichkeit und >>> Unversehrtheit dieser Mitteilung. Bei irrtümlicher Zustellung bitten wir >>> Sie um Benachrichtigung per e-Mail und um Löschung dieser Nachricht sowie >>> eventueller Anhänge. Jegliche unberechtigte Verwendung oder Verbreitung >>> dieser Informationen ist streng verboten. >>> >>> This message is intended only for the named recipient and may contain >>> confidential or privileged information. As the confidentiality of email >>> communication cannot be guaranteed, we do not accept any responsibility for >>> the confidentiality and the intactness of this message. If you have >>> received it in error, please advise the sender by return e-mail and delete >>> this message and any attachments. Any unauthorised use or dissemination of >>> this information is strictly prohibited. >>> >>
