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

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

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

   > > Unfortunately Yetus cannot handle patches this big, I don't think we can 
get CI run via GitHub.
   > 
   > @stoty , we usually break such a large change into several JIRAs. In this 
case, we may
   > 
   > 1. add HadoopThread and change hadoop-common to use it;
   > 2. change HDFS to use HadoopThread;
   > 3. change Mapreduce/YARN to use HadoopThread; and
   > 4. change all the remaining components to use it.
   
   The problem with this is that it would make it impossible to get a clean 
JDK24/25 test run until all the changes are committed, hence all but the last 
commit would be flying blind WRT testing. 
   (It also wouldn't make a lot of sense, as the changes are exactly the same 
for all subprojects)
   
   > 
   > Alternatively, we may work on it in a dev branch.
   
   That sounds better, but I personally don't have the permissions for that.
   Could you (or someone else ) open a feature branch and add this commit ?
   




> 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