[jira] [Updated] (HADOOP-19486) Fully Support Java 25

["Cheng Pan (Jira)" <ji...@apache.org>]

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

Cheng Pan updated HADOOP-19486:
-------------------------------
    Summary: Fully Support Java 25  (was: Fully Support Java 23, 24 and 25)

> Fully Support Java 25
> ---------------------
>
>                 Key: HADOOP-19486
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19486
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Major
>
> Hadoop trunk today mostly supports JDK17, but doesn't work at all on JDK23. (and conversely on JDK24 to be released in less than two weeks)
> While there are many smaller issues, the major breaking change is the SecurityManager removal (JEP411/486), and its many consequences.
> The obvious change is that Subjec.doAs() and Subject.current() no longer work by default, and the replacement APIs must be used.
> The more insidius change is that when SecurityManager is disabled then JDK22+ does not propapage the Subject to new Threads, which is something that Hadoop absolutely relies on.
> Note that Hadoop is always built with with JDK 17  (if the JDK is 17 or newer), unless the target version is specifically overriden.
> This is not a problem, JDK17 class files running on a JDK 24 JVM is the expected use case for binary distributions.
> We may want to run some tests where Hadoop is also compiled for the lastest JVM later. (taget Java 24 + JVM 24)



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

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org