+1 for updating the server side java version. But DiDi has hit one OM performance issue HDDS-11240 <https://issues.apache.org/jira/browse/HDDS-11240> when using JDK 17. Not sure whether JDK 11 will have this issue or not.
On Sat, 16 Nov 2024 at 04:56, Attila Doroszlai <adorosz...@apache.org> wrote: > Hi Apache Ozone community, > > Ozone currently requires minimum Java 8 at both build and run time, > but it compiles and runs fine with newer Java versions. The GitHub CI > workflow includes compilation with Java 11, 17 and 21. Tests are run > with Java 17. > > Java 21 has been GA for more than a year, Java 17 for 3 years now. [1] > > Some third-party dependencies have stopped releasing fixes for > versions that work with Java 8. > - Derby requires Java 21 [2] > - Spring and jOOQ require Java 17 [3], [4] > > These are used only by Recon. > > To continue receiving fixes for these dependencies, we would need to > bump the minimum Java required for building Ozone. We would also > require the same version for running server components. Client > components should still be usable with Java 8. > > I think the next major version, 2.0 would be a good candidate to make > such a move. We should continue to support Java 8 with 1.4.x. > > What do you think? > > -Attila > > [1] https://www.oracle.com/java/technologies/java-se-support-roadmap.html > [2] https://db.apache.org/derby/derby_downloads.html > [3] https://docs.spring.io/spring-framework/reference/6.0/overview.html > [4] https://www.jooq.org/download/versions#oss > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org > For additional commands, e-mail: dev-h...@ozone.apache.org > >
