I just wanted to bump this and see if anyone had more feedback before
trying to call a vote for this for 4.0?
Chris
On Mon, Apr 1, 2024 at 3:41 PM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> Greg,
>
> 1. Ok sounds good we can target JDK 17 in this KIP if we decide to do
Greg,
1. Ok sounds good we can target JDK 17 in this KIP if we decide to do that.
2. For the EE version, I don't think it really matters since we won't be
using any new features that I am aware of. It's just something I noticed
that we will need to pick because Jetty 12 supports multiple versions
Hey Chris,
Thanks for your questions!
1. KIPs are generally immutable once they've been voted on. In this
case, I think it's better that this KIP include the bump to Java 17
just for Connect and MirrorMaker 2, and should include that in the KIP
title.
2. I'm not familiar with the difference, can
Hi Greg,
Thanks for the detailed analysis on the connect framework. It sounds like
hopefully we can go ahead and require JDK 17+ and bump that dependency for
the ConnectRestExtensionContext.
I agree we can leave it open and hear what others think as well about the
requirement, if everyone ends
Hey all,
I looked into how Debezium handled the javax->jakarta changeover for
Quarkus, and found this release note:
https://debezium.io/blog/2023/04/20/debezium-2-2-final-released/#new-quarkus-3
It appears that Debezium 2.1 required Quarkus < 3.0, and Debezium 2.2
required Quarkus >= 3.0. The
Hi Chris,
Thank you so much for opening this KIP, and making sure Kafka keeps up
with the rest of the Java ecosystem!
I took a look around at some Open Source connector implementations,
and checked their Java version support:
* The Aiven connect plugins (http, bigquery, jdbc, elasticsearch,
Hi,
I'm proposing a KIP for Kafka 4.0 to upgrade to to Jakarta and JavaEE 9
APIs. This will also upgrade dependencies like Jetty and move away from
the depcrated javax namespace to be in line with other libraries and
frameworks. There was some initial
