[ 
https://issues.apache.org/jira/browse/FLINK-15736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676613#comment-17676613
 ] 

Chesnay Schepler edited comment on FLINK-15736 at 1/13/23 1:31 PM:
-------------------------------------------------------------------

Really FLINK-24998 is the big one. Everything else we understand the problem 
and have at least a workaround (except maybe FLINK-25006), but that segfault is 
a headscratcher and single-handedly kills this entire effort.


was (Author: zentol):
Really FLINK-24998 is the big one. Everything else we understand the problem 
and have at least a workaround, but that segfault is a headscratcher and 
single-handedly kills this entire effort.

> 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)

Reply via email to