Upgrade to Trino 476

Author: mosabua

.github/workflows/ci.yml

@@ -22,7 +22,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        java-version: [23]
+        java-version: [24]
     timeout-minutes: 20
     steps:
       - name: Checkout source

.mvn/wrapper/maven-wrapper.properties

@@ -16,4 +16,4 @@
 # under the License.
 wrapperVersion=3.3.2
 distributionType=only-script
-distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
+distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.11/apache-maven-3.9.11-bin.zip

README.md

@@ -25,6 +25,29 @@ customizations.
 Find more [information about building and using the custom tarball package in
 the documentation](trino-server-custom/README.md).
 
+## Build
+
+You can build the project with the modules `trino-server-custom` and
+`trino-server-rpm` with the following commands:
+
+```shell
+cd trino-packages
+./mvnw clean install
+```
+
+Including all tests:
+
+```shell
+./mvnw -P ci clean install
+```
+
+More details in the specific module
+[trino-server-custom](trino-server-custom/README.md) and the
+[trino-server-rpm](trino-server-rpm/README.md) README files.
+
+Building the custom Docker image is separate and documented in the
+[custom-docker](custom-docker/README.md) README file.
+
 ## Potential future additions
 
 The following other package ideas are suitable for implementation in this

custom-docker/README.md

@@ -44,7 +44,7 @@ limited subset of plugins to create a image with the following characteristics:
 * `geospatial` functions plugin removed.
 * `exchange-filesystem` plugin removed.
 
-The project is configured for Trino 475.
+The project is configured for Trino 476.
 
 ## Building
 
@@ -73,9 +73,9 @@ processor architectures locally with `docker images`:
 
 ```
 REPOSITORY     TAG           IMAGE ID       CREATED              SIZE
-trino-custom   475-ppc64le   2279b0a14cb6   About a minute ago   790MB
-trino-custom   475-arm64     67a3dcee3c85   About a minute ago   765MB
-trino-custom   475-amd64     df994bb44819   About a minute ago   757MB
+trino-custom   476-ppc64le   2279b0a14cb6   About a minute ago   790MB
+trino-custom   476-arm64     67a3dcee3c85   About a minute ago   765MB
+trino-custom   476-amd64     df994bb44819   About a minute ago   757MB
 ```
 
 The specific version depends on the parameter `TRINO_VERSION` set in `build.sh`.
@@ -92,7 +92,7 @@ purposes. The Trino node functions both as a coordinator and a worker. To launch
 it, execute the following:
 
 ```shell
-docker run -p 8080:8080 --name trino-custom  trino-custom:475-arm64
+docker run -p 8080:8080 --name trino-custom  trino-custom:476-arm64
 ```
 
 Wait for the following message log line:
@@ -155,7 +155,7 @@ other Trino documentation for more details.
 
 ## Updating to other Trino version
 
-The project is configured to build a custom tarball for Trino 475. Updates to
+The project is configured to build a custom tarball for Trino 476. Updates to
 newer versions can be contributed to the repository or can be done locally. The
 following steps are necessary:
 

custom-docker/build.sh

@@ -9,15 +9,15 @@ Builds the Trino Docker image
 
 -h       Display help
 -a       Build the specified comma-separated architectures, defaults to amd64,arm64,ppc64le
--r       Trino version, defaults to 475
+-r       Trino version, defaults to 476
 -t       Image tag name, defaults to trino-custom
 EOF
 }
 
 ARCHITECTURES=(amd64 arm64 ppc64le)
 # Set the desires Trino version. This version is also used automatically in the
 # Dockerfile.
-TRINO_VERSION=475
+TRINO_VERSION=476
 TAG_PREFIX=trino-custom
 
 while getopts ":a:r:t:h" o; do

pom.xml

@@ -5,7 +5,7 @@
     <parent>
         <groupId>io.airlift</groupId>
         <artifactId>airbase</artifactId>
-        <version>253</version>
+        <version>264</version>
     </parent>
 
     <groupId>io.trino</groupId>

trino-server-custom/README.md

@@ -49,15 +49,15 @@ characteristics:
 * `ml` functions plugin from `trino-server-core` removed.
 * `geospatial` functions plugin from `trino-server-core` removed.
 
-The project is configured for Trino 475.
+The project is configured for Trino 476.
 
 ## Building
 
 The build requirements for the project are identical to Trino build
 requirements:
 
 * Linux or MacOS
-* Java 23
+* Java 24
 
 Download and extract or clone the repository to work with the `trino-packages`
 directory locally on your machine.
@@ -84,7 +84,8 @@ After a successful build, you find the tarball in the
 Build the project on any machine, and copy the tarball package from the
 `trino-server-custom/target` directory to the server on which you want to
 install Trino. The server must meet the Trino requirements for the specific
-Trino version, for example Java 23 for Trino 472.
+Trino version, for example Java 23 for Trino 472, or Java 24 for Trino 476 and
+higher.
 
 Find details in the [Trino documentation](https://trino.io/docs/current/installation/deployment.html)
 

trino-server-custom/pom.xml

@@ -13,7 +13,7 @@
     <description>Trino - Server custom tarball package</description>
 
     <properties>
-        <dep.trino.version>475</dep.trino.version>
+        <dep.trino.version>476</dep.trino.version>
         <dep.takari.version>2.2.0</dep.takari.version>
         <air.check.skip-checkstyle>true</air.check.skip-checkstyle>
         <air.check.skip-enforcer>false</air.check.skip-enforcer>

trino-server-rpm/README.md

@@ -21,14 +21,14 @@ The RPM archive contains the application, all plugins, the necessary default
 configuration files, default setups, and integration with the operating system
 to start as a service.
 
-The project is configured for Trino 475.
+The project is configured for Trino 476.
 
 ## Building
 
 The build requirements for the project are identical to Trino build requirements:
 
 * Linux or MacOS
-* Java 23
+* Java 24
 
 Download and extract or clone the repository to work with the `trino-packages`
 directory locally on your machine.

trino-server-rpm/pom.xml

@@ -14,15 +14,15 @@
     <url>https://trino.io</url>
 
     <properties>
-        <project.build.targetJdk>23</project.build.targetJdk>
-        <air.java.version>23.0.0</air.java.version>
+        <project.build.targetJdk>24</project.build.targetJdk>
+        <air.java.version>24.0.2</air.java.version>
         <air.check.skip-spotbugs>true</air.check.skip-spotbugs>
         <air.check.skip-pmd>true</air.check.skip-pmd>
         <air.check.skip-jacoco>true</air.check.skip-jacoco>
         <air.check.skip-duplicate-finder>true</air.check.skip-duplicate-finder>
         <air.modernizer.java-version>8</air.modernizer.java-version>
 
-        <dep.trino.version>475</dep.trino.version>
+        <dep.trino.version>476</dep.trino.version>
         <server.tar.package>trino-server-${dep.trino.version}</server.tar.package>
         <rpm.skipSigning>true</rpm.skipSigning>
     </properties>
@@ -111,7 +111,7 @@
         <dependency>
             <groupId>org.testcontainers</groupId>
             <artifactId>testcontainers</artifactId>
-            <version>1.20.6</version>
+            <version>1.21.3</version>
             <scope>test</scope>
         </dependency>
     </dependencies>
@@ -403,6 +403,7 @@
                     <plugin>
                         <groupId>org.apache.maven.plugins</groupId>
                         <artifactId>maven-failsafe-plugin</artifactId>
+                        <version>${dep.plugin.surefire.version}</version>
                         <configuration>
                             <systemPropertyVariables>
                                 <rpm>${project.build.directory}/trino-server-rpm-${dep.trino.version}.noarch.rpm</rpm>