[
https://issues.apache.org/jira/browse/HADOOP-19574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016676#comment-18016676
]
ASF GitHub Bot commented on HADOOP-19574:
-----------------------------------------
slfan1989 commented on PR #7892:
URL: https://github.com/apache/hadoop/pull/7892#issuecomment-3231655872
@cnauroth @szetszwo Thank you for your responses! Regarding the issue with
Yetus failing to compile, @ayushtkn proposed a solution to handle large PRs. I
suggest we first run this PR to test it, and if it’s suitable for splitting, we
can submit it in parts.
@stoty Thank you for your contribution! Please review the details of this
commit. During development, we need to replace Yetus with Ayush's branch. If
this PR is merged, we should revert this commit.
https://github.com/apache/hadoop/pull/7019/commits/8d636ce31911936d8459b1ef134b1704d55a948e
> 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
