[
https://issues.apache.org/jira/browse/HADOOP-19574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18019759#comment-18019759
]
ASF GitHub Bot commented on HADOOP-19574:
-----------------------------------------
slfan1989 commented on PR #7892:
URL: https://github.com/apache/hadoop/pull/7892#issuecomment-3283565732
@stoty I’d like to confirm with you whether you’d prefer us to create a
separate development branch for you.
Pan and I had an offline discussion on this topic. He believes the changes
are manageable and therefore a separate branch may not be necessary. I think
his point makes sense to some extent, but from the perspective of development
efficiency and risk control, I would still recommend creating a dedicated
development branch. This would allow us to iterate more quickly without
impacting existing functionality.
> Restore Subject propagation semantics for Java 22+
> --------------------------------------------------
>
> Key: HADOOP-19574
> URL: https://issues.apache.org/jira/browse/HADOOP-19574
> Project: Hadoop Common
> Issue Type: Improvement
> 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
