[
https://issues.apache.org/jira/browse/HADOOP-19574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18020348#comment-18020348
]
ASF GitHub Bot commented on HADOOP-19574:
-----------------------------------------
pan3793 commented on PR #7892:
URL: https://github.com/apache/hadoop/pull/7892#issuecomment-3292055686
Kindly ping @szetszwo @steveloughran @cnauroth
We need a final decision here. I think these two approaches are just
different programming patterns, with no essential functionality difference.
Java 25 is coming (scheduled on Sept 26, 2025), and I am eager for a Java
25-compatible Hadoop client to unblock downstream projects to support Java 25.
> 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]
