Hi Kevin, While it's still a non-binding vote I do want to ask you to reconsider given the following:
In the discussion thread I outlined that Flinks Scala APIs can't be removed until Flink 2.0 while Java 17 support can either be added in a new Flink minor version or in a next major version as well. Next to that, I do think that adding Java 17 as a prerequisite does not fit with this proposal. For me they are orthogonal given that they are different technologies. I can see that Java 17 support could potentially ease rewriting your Flink application, but "Java 17 support" doesn't clarify what from Java 17 is needed and you would still loose savepoint compatibility. I would rather start with rewriting your applications now using the Java API, to also benefit from being able to use any Scala version you want now. Best regards, Martijn Op wo 19 okt. 2022 om 16:51 schreef Kevin Lam <kevin....@shopify.com.invalid > > Non-binding -1. > > Aligned with the objections raised by Yaroslav in > https://lists.apache.org/thread/d3borhdzj496nnggohq42fyb6zkwob3h and agree > with his recommendation to support Java 17 as a prerequisite. We use the > Scala APIs extensively and we would like to have an alternative to Scala so > that we can easily keep up with the latest versions of Flink. > > On 2022/10/17 13:38:42 Martijn Visser wrote: > > Hi everyone, > > > > I'm hereby opening a vote for FLIP-265 Deprecate and remove Scala API > > support. The related discussion can be found here [1]. > > > > Voting will be open for at least 72 hours. > > > > Best regards, > > > > Martijn > > https://twitter.com/MartijnVisser82 > > https://github.com/MartijnVisser > > > > [1] https://lists.apache.org/thread/d3borhdzj496nnggohq42fyb6zkwob3h > > > -- Martijn https://twitter.com/MartijnVisser82 https://github.com/MartijnVisser
