[
https://issues.apache.org/jira/browse/HADOOP-19574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016735#comment-18016735
]
ASF GitHub Bot commented on HADOOP-19574:
-----------------------------------------
stoty commented on PR #7892:
URL: https://github.com/apache/hadoop/pull/7892#issuecomment-3232729888
That would take some time @pan3793 .
The problem is that very few of the tests are using Kerberos, and the
subject issue mostly breaks Kerberized clusters.
Making only enough changes to fix the tests would probably lead to a lot of
real work breakages.
We could remove the "unneccessary" changes from the test code.
I'm not sure if Hadoop has a mechanism to run tests on a real cluster
instead of miniclusters. If it does, then many of those changes will be needed
for running tests on kerberized real clusters.
I'm going to run the test sute on JDK24 without the patch, and report the
breakages here.
> 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: [email protected]
For additional commands, e-mail: [email protected]
