Kafka

hi Soby Did you set the internal config group.share.enable=true? That is another switch that allows us to test the share protocol quickly. Best, Chia-Ping On 2025/09/04 20:09:12 Soby Chacko wrote: > Hi, > > When using the Kafka 4.0.0 client, we could enable shared consumers by > providing the following properties in an embedded Kafka environment. > > For example, > > "unstable.api.versions.enable=true", > "group.coordinator.rebalance.protocols=classic,share", > "share.coordinator.state.topic.replication.factor=1", > "share.coordinator.state.topic.min.isr=1" > > When upgrading to Kafka 4.1.0, the same tests work with just the last > two properties. Is that expected? (Basically, I don't need to set > unstable.api.versions.enable or group.coordinator.rebalance.protocols > in 4.1.0). > > The documentation shows something like setting share.version to 1 >...

hi Vinayak thanks for your report. Yes, it is definitely an issue. I have opened https://issues.apache.org/jira/browse/KAFKA-20752 and my team is going to fix it. If you have free cycles, please feel free to take it over. Best, Chia-Ping On 2026/01/02 13:59:05 Vinayak Gaikwad wrote: > Hi team, > > Can anyone provide any suggestions on this issue? > > On Sun, Nov 30, 2025 at 12:29 PM Vinayak Gaikwad < > gaikwadvinayak291@gmail.com> wrote: > > > Hi, > > I am encountering an issue with how timestamp headers are serialized in > > Kafka Connect and would appreciate clarification on whether this is the > > intended behavior or a bug. > > > > Problem: Incorrect Serialization of Midnight UTC Timestamps > > When using connectors that produce timestamp headers (e.g., the MongoDB > > source connector), timestamps that fall exactly at midnight UTC are being > > serialized incorrectly, losi...

Thanks to Bill Bejeck for running the release! Bill Bejeck <bbejeck@apache.org> 於 2026年6月26日週五 上午1:08寫道： > The Apache Kafka community is pleased to announce the release for > Apache Kafka 4.3.1 > > This bug-fix release includes several critical fixes as documented in the > release notes. > > All of the changes in this release can be found in the release notes: > https://www.apache.org/dist/kafka/4.3.1/RELEASE_NOTES.html > > You can download the source and binary release from: > https://kafka.apache.org/downloads#4.3.1 > > > --------------------------------------------------------------------------------------------------- > > > Apache Kafka is a distributed streaming platform with four core APIs: > > > ** The Producer API allows an application to publish a stream of records to > one or more Kafka topics. > > ** The Consumer API allows an application to subscribe to one or more > t...

The Apache Kafka community is pleased to announce the release for Apache Kafka 4.3.1 This bug-fix release includes several critical fixes as documented in the release notes. All of the changes in this release can be found in the release notes: https://www.apache.org/dist/kafka/4.3.1/RELEASE_NOTES.html You can download the source and binary release from: https://kafka.apache.org/downloads#4.3.1 --------------------------------------------------------------------------------------------------- Apache Kafka is a distributed streaming platform with four core APIs: ** The Producer API allows an application to publish a stream of records to one or more Kafka topics. ** The Consumer API allows an application to subscribe to one or more topics and process the stream of records produced to them. ** The Streams API allows an application to act as a stream processor, consuming an input stream from one or more topics and producing an output stream to one or more...

You need to request an account: https://selfserve.apache.org/jira-account.html On 6/24/26 6:02 PM, sunil chaudhari wrote: > H, > How to create Jira ticket for crucial custom parittioning requirement? >

hi Are you looking for an official way to add "labels" to topics? If so, there is no such mechanism for now. One workaround is to create a compacted topic to store them. Another is to encode the labels within the topic name, such as a-b-c-d. If topic-level labels are a crucial feature for you, please feel free to open a JIRA and KIP for it. Best, Chia-Ping On 2026/04/13 03:07:15 Satyaprakash Dwibedi via users wrote: > Hello Kafka Community, > > We have a use case that requires attaching custom metadata to topics — > things like SLA, durability guarantees, and PagerDuty account references. > While exploring this in Kafka 4.2.0, we noticed an interesting > inconsistency between broker-level and topic-level configuration behavior. > > Broker-level custom configs work fine: > > Running the following command succeeds without errors: > > ./bin/kafka-configs.sh --bootstrap-server localhost:9092 \ > --entity-typ...

hi Jesús Have you tried to use `kafka-metadata-quorum.sh` to remove those "offline" nodes from voters? For example: ``` bin/kafka-metadata-quorum.sh --command remove-controller --controller-id ``` Best, Chia-Ping On 2026/05/29 06:32:27 Jesus Cea wrote: > In a personal cluster I used to have three kraft controllers, using > Kafka 4.2.0. > > Because of "reasons" (the cluster is a lab), I downsized the cluster and > now I only use a controller, just modifying "controller.quorum.voters" > to include only the surviving controller. > > Working fine so far. Yes, I know that a single controller is a risk. > > Today I upgraded the brokers and the controller to Kafka 4.3.0 and I > tried to upgrade de cluster version using "kafka-features.sh upgrade > --release-version 4.3", but it is complaining that "old" controllers, > offline and destroyed, are not compatible (they wer...