[
https://issues.apache.org/jira/browse/HADOOP-19574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017718#comment-18017718
]
ASF GitHub Bot commented on HADOOP-19574:
-----------------------------------------
szetszwo commented on PR #7892:
URL: https://github.com/apache/hadoop/pull/7892#issuecomment-3246043904
> You cannot override the run() / work() method if you use a factory.
@stoty , builder is more flexible than constructors. We definitely can
override method as today.
```java
//TestByteArrayManager
static class AllocatorThread extends Thread {
```
```java
// existing code
final AllocatorThread t = new AllocatorThread(arrayLength, bam);
```
Instead of call `new AllocatorThread(..)` above, we will have
```java
// new code
final Thread t = SubjectInheritingThread.newBuilder()
.setThread(new AllocatorThread(arrayLength, bam))
.build();
```
> 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]
