-1 Upgrading the client is harder than upgrading the broker. Pulsar usually acts as a service to serve many lines of business and only a single team is responsible to maintain the server side. It would be hard to push all the client sides to upgrade the JDK.
Instead of upgrading the minimum required JDK of the client, it's better to open a separate project if you think the client with JDK 17 could bring significant performance and security improvements. Thanks, Yunze On Wed, Feb 15, 2023 at 1:08 AM Zixuan Liu <node...@gmail.com> wrote: > > Hi all, > > We are using JDK 17 to compile all the components. For the main component, > the broker and proxy require JDK 17, and the client requires JDK 8. > > In Pulsar 3.x, we should keep up with modern JDKS for all components, and > over time, I believe many users have adopted JDK 11/17, which provides > significant performance and security improvements, see > https://learn.microsoft.com/en-us/java/openjdk/reasons-to-move-to-java-11 > > Switching to JDK17 is a bit radical, and we still need to consider this. > > Thanks, > Zixuan
