[
https://issues.apache.org/jira/browse/FLINK-15736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700173#comment-17700173
]
Rostislav Krasny commented on FLINK-15736:
------------------------------------------
Hello [~martijnvisser]
If the only blocker of this issue is Kryo support of Java 17 then somehow it
should be upgraded. The FLINK-3154 is about upgrading Kryo from 2.24.0 to
5.2.0, however (according to the [Kryo release
notes|https://github.com/EsotericSoftware/kryo/releases]) the very first
version of Kryo with support of Java 17 is 5.2.1. According to the mentioned
above release notes the latest 5.4.0 version of Kryo has some more improvements
of the Java 17 support but in the FLINK-3154 you wrote: "there is currently no
plan for upgrading to a newer version of Kryo because it would break savepoint
compatibility". Is that your comment still relevant and if yes is it possible
to upgrade to a custom version of Kryo 5.2.1 plus those improvement of Java 17
support ([#930|https://github.com/EsotericSoftware/kryo/pull/930],
[#932|https://github.com/EsotericSoftware/kryo/pull/932],
[#933|https://github.com/EsotericSoftware/kryo/pull/933]) from 5.4.0 back
ported? All 5.2.x versions sound like fully compatible with 5.2.0 aren't they?
> Support Java 17 (LTS)
> ---------------------
>
> Key: FLINK-15736
> URL: https://issues.apache.org/jira/browse/FLINK-15736
> Project: Flink
> Issue Type: New Feature
> Components: Build System
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: auto-deprioritized-major, pull-request-available,
> stale-assigned
>
> Long-term issue for preparing Flink for Java 17.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
