Kafka

Hey Christo, could we include fixes for two usability issues in the new RC? They are minor low-risk changes, but it would be good to include them. Let me know, so I can cherry-pick them today. - https://github.com/apache/kafka/commit/7fa5121a172e4ac0248c15e73d5833dcec9bb7d8 - https://github.com/apache/kafka/commit/c552631801f709ff7d1090b99dd5f0053d5c08ce Cheers, Lucas On Mon, Jan 19, 2026 at 11:34 AM Christo Lolov < christololov@gmail.com > wrote: > > Heya David, > > Yes, it makes sense for these to be cherry-picked, I will be creating > RC1 later today, so I will cherry-pick them beforehand, thanks for > bringing these to my attention! > > I am now closing the voting thread for RC0! > > Best, > Christo > > On Fri, 16 Jan 2026 at 13:39, David Jacot via dev < dev@kafka.apache.org > wrote: > > > > Hi Christo, > > > > If we cut a new RC, I wonder if we could include the fixes for ...

Heya David, Yes, it makes sense for these to be cherry-picked, I will be creating RC1 later today, so I will cherry-pick them beforehand, thanks for bringing these to my attention! I am now closing the voting thread for RC0! Best, Christo On Fri, 16 Jan 2026 at 13:39, David Jacot via dev < dev@kafka.apache.org > wrote: > > Hi Christo, > > If we cut a new RC, I wonder if we could include the fixes for > https://issues.apache.org/jira/browse/KAFKA-19233 . They are all very small > changes (with a lot of tests). It may be helpful for Queues and Streams to > go GA. What do you think? > > Best, > Davud > > On Fri, Jan 16, 2026 at 12:23 PM Christo Lolov < christololov@gmail.com > > wrote: > > > Heya Paolo, > > > > Thanks for catching this and providing a fix! It makes sense to me > > that since this is part of Kafka Connect's REST API it is public and > > therefore we can...

Hi Christo, If we cut a new RC, I wonder if we could include the fixes for https://issues.apache.org/jira/browse/KAFKA-19233 . They are all very small changes (with a lot of tests). It may be helpful for Queues and Streams to go GA. What do you think? Best, Davud On Fri, Jan 16, 2026 at 12:23 PM Christo Lolov < christololov@gmail.com > wrote: > Heya Paolo, > > Thanks for catching this and providing a fix! It makes sense to me > that since this is part of Kafka Connect's REST API it is public and > therefore we can't change the output without a corresponding KIP. I > have reviewed the PR and I am happy to cherry-pick it once it has made > it into trunk and include it in RC1. > > Best, > Christo > > On Fri, 16 Jan 2026 at 10:33, Paolo Patierno < paolo.patierno@gmail.com > > wrote: > > > > FYI I opened https://issues.apache.org/jira/browse/KAFKA-20076 and also > a > > correspo...

Heya Paolo, Thanks for catching this and providing a fix! It makes sense to me that since this is part of Kafka Connect's REST API it is public and therefore we can't change the output without a corresponding KIP. I have reviewed the PR and I am happy to cherry-pick it once it has made it into trunk and include it in RC1. Best, Christo On Fri, 16 Jan 2026 at 10:33, Paolo Patierno < paolo.patierno@gmail.com > wrote: > > FYI I opened https://issues.apache.org/jira/browse/KAFKA-20076 and also a > corresponding PR to fix the issue here > https://github.com/apache/kafka/pull/21318 > It's against trunk but I think we should (if/when approved) cherry-pick to > 4.2.0. > > Thanks, > Paolo > > On Thu, 15 Jan 2026 at 17:01, Paolo Patierno < paolo.patierno@gmail.com > > wrote: > > > Hello, > > I think I have found a regression. > > When running Kafka Connect and submitting an HTTP GET r...

FYI I opened https://issues.apache.org/jira/browse/KAFKA-20076 and also a corresponding PR to fix the issue here https://github.com/apache/kafka/pull/21318 It's against trunk but I think we should (if/when approved) cherry-pick to 4.2.0. Thanks, Paolo On Thu, 15 Jan 2026 at 17:01, Paolo Patierno < paolo.patierno@gmail.com > wrote: > Hello, > I think I have found a regression. > When running Kafka Connect and submitting an HTTP GET request to the > /connector-plugins endpoint, the JSON serialized "type" filed in the body > response is now uppercase instead of being lowercase as in the past. > Following a comparison between Apache Kafka 4.1 ... > > > [{"class":"org.apache.kafka.connect.mirror.MirrorCheckpointConnector","type":"source","version":"4.1.1"},{"class":"org.apache.kafka.connect.mirror.MirrorHeartbeatConnector","type":...

Hello Kafka Team, we are observing some unexpected behavior in the Java Kafka client: Problem description: When a KafkaShareConsumer fails to connect to a cluster (because e.g. a port is misconfigured, ...) it enters a busy loop. The symptoms are an excessive amount of logs, high CPU usage and a slowly increasing memory footprint. Software Version: We are using the org.apache.kafka.kafka-clients:4.1.1. Sample: I created a repository with a minimal sample to reproduce the behavior: https://github.com/HenrikLueschenTNG/share-consumer-busy-loop/blob/main/src/main/java/com/example/shareconsumerbusyloop/ShareConsumerBusyLoopApplication.java Details: When the consumer fails to establish a connection, we first see a large amount of identical logs, often many published within the same millisecond: 2026-01-16 07:49:59.311 INFO [consumer_background_thread] org.apache.kafka.clients.Metadata - [ShareConsumer clientId=consumer-test-group-1, groupId=test-group...

Hello, I think I have found a regression. When running Kafka Connect and submitting an HTTP GET request to the /connector-plugins endpoint, the JSON serialized "type" filed in the body response is now uppercase instead of being lowercase as in the past. Following a comparison between Apache Kafka 4.1 ... [{"class":"org.apache.kafka.connect.mirror.MirrorCheckpointConnector","type":"source","version":"4.1.1"},{"class":"org.apache.kafka.connect.mirror.MirrorHeartbeatConnector","type":"source","version":"4.1.1"},{"class":"org.apache.kafka.connect.mirror.MirrorSourceConnector","type":"source","version":"4.1.1"}] ... and the current Apache Kafka 4.2 RC0 [{"class":"org.apache.kafka.connect.mirror.MirrorCheckpointConnector","type":"SOURCE","version...