Hello Vincent, There isn't a firm timeline yet, but the community is rallying around a 3.5.0 release with full support for JDK 17. In addition to the issue you linked, there is also this one:
https://issues.apache.org/jira/browse/HADOOP-17177 Known work related to JDK 17 compatibility is going to be somehow linked off of these. Some of the information in these issues might be stale at this point though. I'd like to take a pass over everything and get a clearer picture of work remaining. Right now, there is a lot of work in progress on upgrading JUnit from 4 to 5. There is a separate work stream on JDK 24 support, and it doesn't have any release plan yet. This requires some more invasive changes in the codebase to handle JDK APIs that were removed after Java 17. Thanks to this patch, we at least have the ability to test with JDK 24 and react to what we find: https://issues.apache.org/jira/browse/HADOOP-19495 Any help you can offer with additional testing and fixes for what you discover (on either JDK 17 or 24) would be welcome! Otherwise, I recommend that you continue to watch this list as we all collaborate on the plan for a new release. Chris Nauroth On Wed, Mar 26, 2025 at 9:02 AM Vincent Russell <vincent.russ...@gmail.com> wrote: > Hello, > > I see that this ticket https://issues.apache.org/jira/browse/HADOOP-18887 > has been created. > > My project uses hdfs and yarn with mapreduce and would like to upgrade our > code base to at least jdk 17 from jdk 11. > > Is upgrading to JDK17 (or maybe even jdk 20 at this point) something that > is still desired? > > I am willing to work on this effort, but I am not sure where to start. > > Thanks, > Vincent >
