You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2023/04/24 09:36:00 UTC

[jira] [Closed] (FLINK-30455) Avoid "cleaning" of java.lang.String in ClosureCleaner

     [ https://issues.apache.org/jira/browse/FLINK-30455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler closed FLINK-30455.
------------------------------------
    Resolution: Duplicate

More general approach suggested in FLINK-31919.

> Avoid "cleaning" of java.lang.String in ClosureCleaner
> ------------------------------------------------------
>
>                 Key: FLINK-30455
>                 URL: https://issues.apache.org/jira/browse/FLINK-30455
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / Core
>            Reporter: Gunnar Morling
>            Assignee: Gunnar Morling
>            Priority: Major
>              Labels: pull-request-available
>
> When running a simple "hello world" example on JDK 17, I noticed the closure cleaner tries to reflectively access the {{java.lang.String}} class, which fails due to the strong encapsulation enabled by default in JDK 17 and beyond. I don't think the closure cleaner needs to act on {{String}} at all, as it doesn't contain any inner classes. Unless there are objections, I'll provide a fix along those lines. With this change in place, I can run that example on JDK 17.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)