[VOTE] 3.4.1 RC0

Hello Kafka users, developers and client-developers, This is the first candidate for release of Apache Kafka 3.4.1. This is a bugfix release with several fixes since the release of 3.4.0. A few of the major issues include: - core KAFKA-14644

Re: [DISCUSS] KIP-931: Flag to ignore unused message attribute field

Good idea! I've created a wiki for the ideas for message format v.3, and added the link in this KIP. https://cwiki.apache.org/confluence/display/KAFKA/ideas+for+kafka+message+format+v.3 Thanks. Luke On Tue, May 16, 2023 at 4:30 PM Ismael Juma wrote: > Perhaps we can start a wiki page where we

Re: [VOTE] KIP-927: Improve the kafka-metadata-quorum output

+1 (non binding) Divij Vaidya On Tue, May 16, 2023 at 4:35 AM ziming deng wrote: > Thanks for this improvement, +1 from me(binging) > > — > Best, > Ziming > > > On May 16, 2023, at 00:43, Federico Valeri wrote: > > > > Hi all, > > > > I'd like to start a vote on KIP-927: Improve the

Re: [DISCUSS] KIP-926: introducing acks=min.insync.replicas config

Hi, Inline with the *backup-only* replica approach, KIP-491: Preferred Leader Deprioritized List was proposed to mark a replica as the lowest priority to become leader. On Sat, May 13, 2023 at 6:53 AM 67 wrote: >

Re: [DISCUSS] Re-visit end of life policy

My impression is also that a lot of users run older, out of EOL, versions of Kafka. The final 3.x version is particularly concerning, as it will be the last bridge to migrate away from ZK. If a big portion of users only upgrade after its EOL period, we might only then discover an important bug

Re: Feature Discussion: Enhancing Kafka Connect's transformation interface to 1 -> Many / Many -> Many

Hi Rabin, I like this idea but it presents challenges for delivery semantics, especially (though not exclusively) with sink connectors. If a sink connector uses the SinkTask::preCommit method [1] to explicitly notify the Connect runtime about which offsets are safe to commit, it may mistakenly

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.4 #133

See

Feature Discussion: Enhancing Kafka Connect's transformation interface to 1 -> Many / Many -> Many

Hi Team, We have a few use cases where nested record with array needs to be flattened / exploded to multiple rows and write it to destination like Cassandra. Now current Transformation interface in Kafka connect takes one record and returns one / zero record. Also current flatten ignores the

[jira] [Created] (KAFKA-14998) Kafka server start fails with the following error java.lang.NumberFormatException: For input string: "a"

Nikilesh created KAFKA-14998: Summary: Kafka server start fails with the following error java.lang.NumberFormatException: For input string: "a" Key: KAFKA-14998 URL: https://issues.apache.org/jira/browse/KAFKA-14998

Re: [DISCUSS] KIP-931: Flag to ignore unused message attribute field

Perhaps we can start a wiki page where we collect these ideas as a precursor to a KIP for record format v3? Ismael On Mon, May 15, 2023, 8:19 PM Luke Chen wrote: > Hi Divij and Ismael, > > Thanks for your great comments. > Yes, I know record format changes are _extremely expensive_ for the >

Migration from zookeeper to kraft not working

Hello! I have a problem with my kafka configuration (kafka 3.4). I'm trying to migrate from zookeeper to kraft. I have 3 brokers, on one of them was also the zookeeper. I want to restart my brokers one by one, without having downtime. I started with putting the configuration with also kraft and