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

ASF GitHub Bot commented on HADOOP-19574:
-----------------------------------------

slfan1989 commented on PR #7892:
URL: https://github.com/apache/hadoop/pull/7892#issuecomment-3228107396

   > This is final piece for Java 24 / 25 support. While the patch is huge, the 
actual changes are very simple. HadoopThread was added and Daemon was modified, 
the rest is just simply replacement.
   > 
   > Please take a look @pan3793 @slfan1989 @jojochuang @cnauroth @steveloughran
   
   I have a few experienced members to recommend for the review. 
   
   @Hexiaoqiao @ayushtkn @szetszwo I need your help to collaboratively review 
this PR. Thank you very much!
   
   




> Restore Subject propagation semantics for Java 22+
> --------------------------------------------------
>
>                 Key: HADOOP-19574
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19574
>             Project: Hadoop Common
>          Issue Type: Bug
>            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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to