Use and require Java 24

[wendigo]

This issues aims to detail and track the progress towards adopting Java 24 as build and runtime requirement for Trino.

Background and motivation

Trino completely adopted Java 23 as of Trino 45x. See https://trino.io/blog/2024/09/17/java-23 and https://trino.io/docs/current/release/release-45x.html. Java 24 is an STS release of Java.

Java 24 is a STS Java release and scheduled to ship in March 2025. Adoption timing in Trino will depend on testing results and feedback, as well as the time for implementation and collaboration with Trino community members.

Specifically, for Java 24, these are some features that we want to be able to leverage:

• Performance improvements to MemorySegment (mismatch, copy, fill)
• JEP 475: Late Barrier Expansion for G1

Proposed schedule for JDK 24 release is:

• 2024/12/05 Rampdown Phase One (branch from main line)
• 2025/01/16 Rampdown Phase Two
• 2025/02/06 Initial Release Candidate
• 2025/02/20 Final Release Candidate
• 2025/03/18 General Availability

The plan is to test and ensure runtime and compile JDK 24 compatibility before GA.

Implementation

Following steps are roughly in order:

• CI build with Java 24 EA in parallel to Java 23
• Blog post about plan to adopt Java 24, @mosabua
• Update dependencies as required to support Java 24, @wendigo
• Update JVM in docker container to Java 24, @wendigo
• Wait for official release of Java 24 and Eclipse Temurin binaries (if necessary in terms of timing)
• Ship a release with the updated container image
• Update build, docs, and runtime to require Java 24
• Ship a release with new requirement, announce and update blog post

Outstanding issues

Following issues were identified:

• Hive JDBC driver used in tests uses Subject.callAs (Update to Java 21 and patch getSubject usages trino-hive-jdbc#6)
• Kafka client doesn't work after SecurityManager removal (see KAFKA-17078: Add SecurityManagerCompatibility shim apache/kafka#16522)
• Trino JDBC driver is using Subject.getSubject() (Support post JDK 17 Subject.current #24197)
• Kudu is using Subject.getSubject() (https://issues.apache.org/jira/browse/KUDU-3627)

[wendigo]

Started testing JDK 24-ea here: #23501