+1 for moving the server to JDK 17 while keeping clients on JDK 8. It will make maintenance much easier and let us modernize the server, without breaking things for our users.
For the downside mentioned above by others, I suggest we: 1. Make sure we have a clear consensus from the community. 2. Create a tracking issue to plan the work, including a target release and a checklist (build, CI, docs, docker image, etc.). 3. Get the infrastructure and upgrade guides ready ahead of time to make the transition smooth for users. Best regards, Minghuang Li On 2025/07/09 08:03:02 Fanng wrote: > Hi, > I want to propose a discussion about upgrading the minimum JDK > version of the Gravitino server to 17 while keeping the Gravitino > client and Spark&Flink connector JDK version to 8 to keep > compatibility. > Recently, I'm working on upgrading the Iceberg version from 1.6 to > 1.9 for IRC to support more interfaces. Still, Iceberg 1.7 drops the > support for JDK8, so I had to split Iceberg code to common-module > which contains legacy code for old version and modern-module which > contains the code for Iceberg new version. User could choose the > Iceberg version when compiling Gravitino, and we should provide > Gravitino server and IRC server for old and new Iceberg version > seperately. Please refer to > https://github.com/apache/gravitino/pull/7418 for more details. It's > hard to maintain for both the developer and the user. > So how about upgrading our Gravitino server min JDK version to 17 > and leave Gravitino clients and connectors to 8, just like Trino > server using High JDK version while Trino client using low JDK > version? This will make the trade-off better for compatibility and > simple usage, and maintenance of Gravitino. > > > Best, > Xiaojing >
