Hi Greg, I think new JDK support is a new feature rather than a bugfix. So we wouldn't include it in 3.9.x for that reason.
It may be a compatible new feature, of course (most new features are...) but still a new feature. I'll comment more on the KIP-1006 thread... my main comment there is that I'd like to understand more about what actual Kafka release will remove SecurityManager before we vote (sounds like it won't be 4.0). best, Colin On Thu, Sep 26, 2024, at 10:29, Greg Harris wrote: > Hey Colin, > > KIP-1006 and the associated vote are about removing support for > SecurityManager, which is a user-facing breaking change. > The PR is an internal-facing, backwards-compatible change that I motivated > and described in the KIP as an interim solution, and doesn't require the > vote to pass in order to be merged. > >> I think supporting new JDK versions that we haven't supported before > should be a 4.0 thing. > > Sure, especially as we don't have any infrastructure for testing Java 23 > set up at the moment. This is possibly the first most obvious compatibility > problem, but there could be more. > > I'll plan on including this in 3.9.1, thanks! > Greg > > On Thu, Sep 26, 2024 at 10:16 AM Colin McCabe <cmcc...@apache.org> wrote: > >> Hi all, >> >> I wanted to give a quick update on the 3.9.0 release. >> >> We had several fixes in the last few days (KAFKA-17459, KAFKA-17584, etc.) >> and uncovered two new blocker bugs which now have PRs available >> (KAFKA-17608, KAFKA-17604). Once those are in, I'll create a new RC. >> >> thanks, all. >> Colin >> >> On Thu, Sep 26, 2024, at 10:12, Colin McCabe wrote: >> > Hi Greg, >> > >> > Thank you for working on this. Isn't this work part of KIP-1006? That >> > KIP hasn't even been approved (although it seems very likely to be so). >> > Certainly it isn't in 3.9. The PR is also kind of large with 16 files >> > changed. I think supporting new JDK versions that we haven't supported >> > before should be a 4.0 thing. >> > >> > best, >> > Colin >> > >> > >> > On Thu, Sep 26, 2024, at 09:44, Greg Harris wrote: >> >> Hi Colin, >> >> >> >> It has been brought to my attention that Java 23 is now GA, and Kafka >> >> clients, brokers, and connect are now experiencing >> >> UnsupportedOperationExceptions by default due our use of the >> >> deprecated-for-removal SecurityManager. >> >> This only happens upon upgrading to Java 23, so this is not a >> regression. >> >> Users can workaround this issue themselves by setting a system property >> or >> >> by not upgrading to Java 23. >> >> >> >> I have implemented a patch to avoid these >> UnsupportedOperationExceptions, >> >> and effectively make Kafka compatible with Java 23 by default. >> >> Issue: https://issues.apache.org/jira/browse/KAFKA-17078 and the >> associated >> >> PR: https://github.com/apache/kafka/pull/16522 >> >> The patch has low risk for users which don't use SecurityManager. It >> has a >> >> moderate risk for users that use SecurityManager, as we don't have good >> >> visibility into those use-cases. >> >> >> >> Is this something that you want to include in 3.9.0? >> >> >> >> Thanks, >> >> Greg >> >> >> >> On Wed, Sep 25, 2024 at 2:31 PM José Armando García Sancio >> >> <jsan...@confluent.io.invalid> wrote: >> >> >> >>> Hi Colin, >> >>> >> >>> We found a bug that we should fix for 3.9.0 >> >>> (https://issues.apache.org/jira/browse/KAFKA-17608). Alyssa is going >> >>> to work on the fix and we expect a PR soon. >> >>> >> >>> Thanks, >> >>> -José >> >>> >>
