[ https://issues.apache.org/jira/browse/HADOOP-19574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016775#comment-18016775 ]
ASF GitHub Bot commented on HADOOP-19574: ----------------------------------------- pan3793 commented on code in PR #7892: URL: https://github.com/apache/hadoop/pull/7892#discussion_r2307314275 ########## hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/concurrent/HadoopThread.java: ########## @@ -0,0 +1,105 @@ +/** + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +package org.apache.hadoop.util.concurrent; + +import java.security.PrivilegedAction; +import javax.security.auth.Subject; + +import org.apache.hadoop.security.authentication.util.SubjectUtil; + +/** + * Helper class to restore Subject propagation behavior after the JEP411/JEP486 + * changes + * + * Runnables can be specified normally, but the work() method has to be + * overridden instead of run() when subclassing. + */ +public class HadoopThread extends Thread { Review Comment: Hadoop has MiniKDC in the test infrastructure, is it possible to have a dedicated UT for `HadoopThread`, so that we can test against different JDK versions to ensure the consistent semantics of Subject propagation? and downstream projects that require Subject propagation also need to change their code, right? > 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