[
https://issues.apache.org/jira/browse/HADOOP-19574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18037345#comment-18037345
]
ASF GitHub Bot commented on HADOOP-19574:
-----------------------------------------
slfan1989 commented on PR #7892:
URL: https://github.com/apache/hadoop/pull/7892#issuecomment-3515111609
@stoty Thank you very much for your continued efforts in advancing this
feature. However, I believe we should take a bit more time and proceed with
patience. At present, Hadoop has only just completed support for `JDK 17` and
`JDK 21`, and there are still some outstanding issues in the trunk branch—for
example, `SpotBugs` and `jdiff` have not yet been fully resolved. The current
build still shows quite a few errors and has not reached a fully `green` state.
Given this situation, I don’t think there’s a need to rush into supporting
the newly released `JDK 25`. Shouldn’t we first ensure that the work for `JDK
17` and `JDK 21` is fully completed and the build is stable before moving
forward with `JDK 25` support?
cc: @pan3793
> Restore Subject propagation semantics for Java 22+
> --------------------------------------------------
>
> Key: HADOOP-19574
> URL: https://issues.apache.org/jira/browse/HADOOP-19574
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Critical
> Labels: pull-request-available
>
> Java 22 breaks Subject propagation for new Threads (when SecurityManager is
> not enabled).
> Previously, the Subject set by Subject.doAs() / Subject.callAs()
> automatically propagated to any new Threads created (via new Thread(), not
> Executors).
> With JDK22, this is no longer the case, new Threads do NOT inherit the
> Subject.
> As Hadoop heavily relies on the original behavior, we somehow need to solve
> this problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
