[ 
https://issues.apache.org/jira/browse/HADOOP-19668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036095#comment-18036095
 ] 

ASF GitHub Bot commented on HADOOP-19668:
-----------------------------------------

stoty opened a new pull request, #8061:
URL: https://github.com/apache/hadoop/pull/8061

   ### Description of PR
   
   First part of HADOOP-19574. 
   Add SubjectInheritingThread and update Daemon, but only update the classes 
using Daemon
   
   ### How was this patch tested?
   
   Tested together with HADOOP-19670. 
   Ran the full test suite with JDK25, and confirmed that it does not cause 
regressions
   (i.e. only tests which also fail with Java 17 fail with Java 25)
   
   ### For code changes:
   
   - [X] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> Add SubjectInheritingThread to restore pre JDK22 Subject behaviour in Threads
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-19668
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19668
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: security
>    Affects Versions: 3.5.0
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Major
>
> This is the first part of HADOOP-19574 which adds the compatibility code, and 
> fixes Daemon, but does not replace native Thread instances.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to