[
https://issues.apache.org/jira/browse/HADOOP-19574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035107#comment-18035107
]
ASF GitHub Bot commented on HADOOP-19574:
-----------------------------------------
steveloughran commented on PR #7892:
URL: https://github.com/apache/hadoop/pull/7892#issuecomment-3481625634
right, what is the state of things. As far as I can tell
* trunk is java17+ only
* @stoty has been running locally and not seeing any more failures than trunk
* lots of reviews including by @szetszwo @slfan1989, @cnauroth and more
* it touches enough files that every week it's not merged there's rebase
pain.
I think we should merge it unless there's a veto from some of the reviewers.
I don't want to make code quality worse, and the JUnit 5 move was fairly hard
work for all -but this is being forced on us by oracle
> 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]
