Re: KafkaProducer partitionsFor v/s KafkaAdminClient describeTopics

Hi Anand, AdminClient is more recommended to get cluster/broker/topic/partition/replication metadata and these apis are under evolving , KafkaProducer is mostly used to produce record and less used to query metadata information. Ziming > On Jun 10, 2025, at 10:33 PM, Subra I wrote: > > Hi A

[jira] [Created] (KAFKA-19399) The version and source link in the `NOTICE-binary` file for `Mockito` are inconsistent

Palak Kapoor created KAFKA-19399: Summary: The version and source link in the `NOTICE-binary` file for `Mockito` are inconsistent Key: KAFKA-19399 URL: https://issues.apache.org/jira/browse/KAFKA-19399

[jira] [Resolved] (KAFKA-18042) Reject the produce request with lower producer epoch early.

[ https://issues.apache.org/jira/browse/KAFKA-18042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justine Olshan resolved KAFKA-18042. Fix Version/s: 4.1.0 Resolution: Fixed > Reject the produce request with lower prod

[jira] [Resolved] (KAFKA-18202) Reject non-zero sequences when there is no producer ID state on the partition for transactions v2 idempotent producers

[ https://issues.apache.org/jira/browse/KAFKA-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justine Olshan resolved KAFKA-18202. Fix Version/s: 4.1.0 Resolution: Fixed > Reject non-zero sequences when there is no

Upcoming Kafka conference

Hi All, Current is a conference dedicated to data streaming, Apache Kafka®, Apache Flink®, and Apache Iceberg™ communities. Now is the time to apply your ideas and experiences to share with the community. The Current 2025 CFP is open *until June

[jira] [Created] (KAFKA-19398) Error getting oldest-iterator-open-since-ms causes NPE in micrometer

Arne Klein created KAFKA-19398: -- Summary: Error getting oldest-iterator-open-since-ms causes NPE in micrometer Key: KAFKA-19398 URL: https://issues.apache.org/jira/browse/KAFKA-19398 Project: Kafka

[jira] [Resolved] (KAFKA-19391) Update the opentelemetry-proto and protobuf

[ https://issues.apache.org/jira/browse/KAFKA-19391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-19391. Fix Version/s: 4.2.0 Resolution: Fixed > Update the opentelemetry-proto and protobu

Re: [DISCUSS] Apache Kafka 4.1.0 release

Hi Chia-Ping, There isn't anything specific to 4.1.0, same rules as usual apply. After feature freeze, we shouldn't merge new major features into 4.1. Stabilization fixes are fine. There is some flexibility with minor features but always communicate and ask in the release thread (here). Bug fixes

[jira] [Resolved] (KAFKA-19389) High memory consumption for completed share fetch requests

[ https://issues.apache.org/jira/browse/KAFKA-19389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-19389. --- Resolution: Fixed > High memory consumption for completed share fetch requests > ---

[jira] [Resolved] (KAFKA-19325) improve forceComplete() in DelayedOperation

[ https://issues.apache.org/jira/browse/KAFKA-19325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-19325. - Resolution: Won't Fix It seems that changing forceComplete() to return void makes the usage less conven

Re: [DISCUSS] Apache Kafka 4.1.0 release

Hi, With the help of Infra I was able to create the new 4.1 branch: https://github.com/apache/kafka/tree/4.1 I'll explain the issue I found in another thread. Thanks, Mickael On Tue, Jun 10, 2025 at 2:53 PM Mickael Maison wrote: > > Hi, > > We are now past feature freeze. > My plan was to cut t

Re: [DISCUSS] Apache Kafka 4.1.0 release

hi Mickael Thanks for managing the 4.1 branch. Are there any rules of backporting to 4.1 that we need to know? Best, Chia-Ping Mickael Maison 於 2025年6月10日 週二 下午11:47寫道： > Hi, > > With the help of Infra I was able to create the new 4.1 branch: > https://github.com/apache/kafka/tree/4.1 > I'll

Re: [DISCUSS] KIP-1172: Improve EndToEndLatency tool

hi Nick thanks for this proposal. Some questions are listed below. chia_0: This tool is used by e2e, so could you please describe the changes for e2e too? chia_1: the two new fields (*message-key-size-byt and * *message-header-size-bytes)* are NOT supported by old (index) arguments, right? If so

Branch protections prevent creating new branches

Hi, A few weeks ago we added branch protection rules to the repository. You can see the current rules in https://github.com/apache/kafka/rules/4026327 One of the rules we have is "Require linear history" which "Prevent merge commits from being pushed to matching refs.". The issue is that we have

New release branch 4.1

Hi, We now have a release branch for 4.1 release (with 4.1.0 as the version). I opened a PR bumping trunk to 4.2.0-SNAPSHOT: https://github.com/apache/kafka/pull/19944 I'll be going over the JIRAs to move every non-blocker from this release to the next release. >From this point, most changes sho

[DISCUSS] KIP-1172: Improve EndToEndLatency tool

Hi everyone, I would like to start a discussion on a KIP to improve the `EndToEndLatency` tool. KIP Link: https://cwiki.apache.org/confluence/x/Awu9F Thank you! Best regards, Nick Guo

KafkaProducer partitionsFor v/s KafkaAdminClient describeTopics

Hi All, I need to know the number of partitions for a topic before producing/consuming. Some users may set the number of partitions for a given topic but some users may just set the number of partitions in server.properties. It should work for both cases. Which method is better for a production g

Re: [DISCUSS] Apache Kafka 4.1.0 release

Hi, We are now past feature freeze. My plan was to cut the 4.1 branch today, but with the new branch protection rules we set [0] I'm not able to do so at the moment. I opened a Jira against Infra [1] and hopefully that will be sorted soon. I'll post another update once the branch is cut. Thanks,

[jira] [Created] (KAFKA-19397) TransactionManager.handleCompletedBatch throws NPE

Lucas Brutschy created KAFKA-19397: -- Summary: TransactionManager.handleCompletedBatch throws NPE Key: KAFKA-19397 URL: https://issues.apache.org/jira/browse/KAFKA-19397 Project: Kafka Issue

[VOTE] KIP-1138: Clean up TopologyConfig and API for supplying configs needed by the topology

Hi, I'd like to start a for KIP-1138 Clean up TopologyConfig and API for supplying configs needed by the topology : https://cwiki.apache.org/confluence/display/KAFKA/KIP-1138%3A+Clean+up+TopologyConfig+and+API+for+supplying+configs+needed+by+the+topology This KIP aims to address several issues r

[jira] [Created] (KAFKA-19396) Use batched version of offset fetch request in new GroupCoordinator interface

Rajini Sivaram created KAFKA-19396: -- Summary: Use batched version of offset fetch request in new GroupCoordinator interface Key: KAFKA-19396 URL: https://issues.apache.org/jira/browse/KAFKA-19396 Pro

[jira] [Resolved] (KAFKA-19392) `metadata.log.segment.ms` is not applied

[ https://issues.apache.org/jira/browse/KAFKA-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-19392. Resolution: Fixed > `metadata.log.segment.ms` is not applied > ---

Re: [PR] MINOR: add CVE-2025-27817,CVE-2025-27818,CVE-2025-27819 [kafka-site]

chia7712 commented on PR #694: URL: https://github.com/apache/kafka-site/pull/694#issuecomment-2958202679 LGTM -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscrib