[ 
https://issues.apache.org/jira/browse/HBASE-29728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth updated HBASE-29728:
--------------------------------
    Description: 
Hadoop trunk now supports Java 25, and is planning to backport it and release 
3.4.3 with JDK25 support.

We can start working on Hadoop 3.5 support now, or wait for the next official 
Hadoop release with JDK25 support.

The Subject changes will be hopefully handled by the Hadoop UGI changes, but we 
will have to :
* duplicate the SubjectInheritingThread mess
* Remove SecurityManager usage
* Fix all the smaller incompatibilities
* If going with 3.5, then solve any Hadoop API incompatibilities

  was:
Hadoop trunk now supports Java 25, and is planning to backport it and release 
3.4.3 with JDK25 support.

We can start working on Hadoop 3.5 support now, or wait for the next official 
Hadoop release with  JDK25 support.

The Subject changes will be hopefully handled by the UGI changes, but we will 
have to 
* duplicate the SubjectInheritingThread mess
* Remove SecurityManager usage
* Fix all the smaller incompatibilities
* If going with 3.5, then solve any Hadoop API incompatibilities


> Support Java 25
> ---------------
>
>                 Key: HBASE-29728
>                 URL: https://issues.apache.org/jira/browse/HBASE-29728
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Istvan Toth
>            Priority: Major
>
> Hadoop trunk now supports Java 25, and is planning to backport it and release 
> 3.4.3 with JDK25 support.
> We can start working on Hadoop 3.5 support now, or wait for the next official 
> Hadoop release with JDK25 support.
> The Subject changes will be hopefully handled by the Hadoop UGI changes, but 
> we will have to :
> * duplicate the SubjectInheritingThread mess
> * Remove SecurityManager usage
> * Fix all the smaller incompatibilities
> * If going with 3.5, then solve any Hadoop API incompatibilities



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

Reply via email to