[
https://issues.apache.org/jira/browse/HADOOP-19574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18019289#comment-18019289
]
ASF GitHub Bot commented on HADOOP-19574:
-----------------------------------------
pan3793 commented on PR #7892:
URL: https://github.com/apache/hadoop/pull/7892#issuecomment-3273429535
> Do you think we should implement and use Thread Builder approach in this
patch ? (see my reservations above)
I think introducing Builder here is a kind of overdesign. @szetszwo do you
have cases in your mind that can not be covered by @stoty's approach? If not, I
strongly support @stoty's approach.
> Is the way I split the patch acceptable (patches without JIRA id will be
merged into the other ones)
Thanks for splitting! I think HADOOP-19668 and HADOOP-19669 can be committed
together; the current state is also fine.
> What other changes (if any) do you think are necessary for patch to be
accepted?
I think it's already in good shape.
> 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: [email protected]
For additional commands, e-mail: [email protected]
