Hey dev community,

I'm writing this email to kick off a discussion following this epic: 
FLINK-15736<https://issues.apache.org/jira/browse/FLINK-15736>.

We are moving towards JDK 17 (LTS) , the only blocker now is Flink which 
currently remains on JDK 11 (LTS). Flink does not support JDK 17 yet, with no 
timeline,  the reason, based on the aforementioned ticket is the following 
tickets

  1.  FLINK-24998 - SIGSEGV in Kryo / C2 CompilerThread on Java 
17<https://issues.apache.org/jira/browse/FLINK-24998>.
  2.  FLINK-3154 - Update Kryo version from 2.24.0 to latest Kryo LTS 
version<https://issues.apache.org/jira/browse/FLINK-3154>

My question is whether it is possible to release a major version (Flink 2.0.0) 
using the latest Kryo version for those who don't need to restore old 
savepoints/checkpoints in newer format.

  1.  Leverage JDK 17 features within JVM
  2.  Moving from the old format to the newer one will be handled only once - a 
mitigation can be achieved by a conversion tool or external serializers, both 
can be provided later on.

I'd like to emphasize that the next JDK LTS (21) will be released this 
September.  furthermore, Flink already supports JDK 12-15, which is very close 
to JDK 17 (LTS) - that was released in September 2021.  JDK 11 will become a 
legacy soon, as more frameworks moving towards JDK 17 and are less likely to 
support JDK 11 in the near future. (For example, Spring Boot 3 requires JDK 17 
already).

Thank you for your consideration of my request.

Tamir.




Confidentiality: This communication and any attachments are intended for the 
above-named persons only and may be confidential and/or legally privileged. Any 
opinions expressed in this communication are not necessarily those of NICE 
Actimize. If this communication has come to you in error you must take no 
action based on it, nor must you copy or show it to anyone; please 
delete/destroy and inform the sender by e-mail immediately.
Monitoring: NICE Actimize may monitor incoming and outgoing e-mails.
Viruses: Although we have taken steps toward ensuring that this e-mail and 
attachments are free from any virus, we advise that in keeping with good 
computing practice the recipient should ensure they are actually virus free.

Reply via email to