Re: [DISCUSS] KIP-1092: Extend Consumer#close with an option to leave the group or not

Hi Sophie, I think you've mentioned a very important distinction between Kafka Streams and Plain Consumer behavior on closing. While KafkaStreams has a ensures state cleanup through its internal mechanism (not sure this statement is accurate or not), Plain Consumer relies on `onPartitionRevoke` ca

Re: [DISCUSS] Does changing help messages for tools require a KIP?

Hi Kirk, Thanks for raising this. In this case, the documentation is wrong so, in my opinion, we could just fix it. Best, David On Thu, Jan 9, 2025 at 2:52 AM Kirk True wrote: > Hi all, > > Do we consider the CLI help/usage message as part of the publicly > documented API? > > Background: Ther

[jira] [Resolved] (KAFKA-18435) Remove zookeeper dependencies in build.gradle

[ https://issues.apache.org/jira/browse/KAFKA-18435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18435. Resolution: Fixed trunk: https://github.com/apache/kafka/commit/c28d9a348670f9efc599b4813

Jenkins build is still unstable: Kafka » Kafka PowerPC Daily » test-powerpc #173

See

[jira] [Created] (KAFKA-18456) Fix flaky PlaintextConsumerPollTest#testMaxPollIntervalMsShorterThanPollTimeout

Chia-Ping Tsai created KAFKA-18456: -- Summary: Fix flaky PlaintextConsumerPollTest#testMaxPollIntervalMsShorterThanPollTimeout Key: KAFKA-18456 URL: https://issues.apache.org/jira/browse/KAFKA-18456 P

[jira] [Created] (KAFKA-18455) Add logs or metrics when connection count exceeds

Luke Chen created KAFKA-18455: - Summary: Add logs or metrics when connection count exceeds Key: KAFKA-18455 URL: https://issues.apache.org/jira/browse/KAFKA-18455 Project: Kafka Issue Type: Impro

[DISCUSS] Does changing help messages for tools require a KIP?

Hi all, Do we consider the CLI help/usage message as part of the publicly documented API? Background: There's a bug in the help/usage message in some of the Kafka CLI tools. For some of the tools that accept a timestamp, the help message instructs the user to provide a date in a '-MM-DDTHH

[jira] [Resolved] (KAFKA-18111) Add Kafka Logo to README

[ https://issues.apache.org/jira/browse/KAFKA-18111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-18111. - Resolution: Fixed > Add Kafka Logo to README > > >

[jira] [Resolved] (KAFKA-18112) Add Kafka Logo to README

[ https://issues.apache.org/jira/browse/KAFKA-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-18112. - Resolution: Fixed > Add Kafka Logo to README > > >

Re: [DISCUSS] KIP-1092: Extend Consumer#close with an option to leave the group or not

tl;dr: 1) I tend to agree we should keep the existing behavior, but what this means is actually different and more complicated than just "if leaves group, then invokes leave callback" 2) Personally I think we should actually *always* invoke this callback, for every case Longer version: First, to

[jira] [Resolved] (KAFKA-18432) Remove unused code from AutoTopicCreationManager

[ https://issues.apache.org/jira/browse/KAFKA-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18432. Fix Version/s: 4.0.0 Resolution: Fixed trunk: https://github.com/apache/kafka/comm

[jira] [Resolved] (KAFKA-18434) enrich the authorization error message of connecting to controller

[ https://issues.apache.org/jira/browse/KAFKA-18434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divij Vaidya resolved KAFKA-18434. -- Resolution: Fixed > enrich the authorization error message of connecting to controller > -

[jira] [Resolved] (KAFKA-18426) Remove FinalizedFeatureChangeListener

[ https://issues.apache.org/jira/browse/KAFKA-18426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18426. Resolution: Fixed trunk: https://github.com/apache/kafka/commit/af3f9e3a5adf3379b178b8587

[jira] [Created] (KAFKA-18454) Migrate Build Scan publication to develocity.apache.org

Clay Johnson created KAFKA-18454: Summary: Migrate Build Scan publication to develocity.apache.org Key: KAFKA-18454 URL: https://issues.apache.org/jira/browse/KAFKA-18454 Project: Kafka Issue

[jira] [Created] (KAFKA-18453) Add StreamsToplogy class

Bruno Cadonna created KAFKA-18453: - Summary: Add StreamsToplogy class Key: KAFKA-18453 URL: https://issues.apache.org/jira/browse/KAFKA-18453 Project: Kafka Issue Type: Sub-task R

[jira] [Resolved] (KAFKA-18321) Add StreamsGroupMember, MemberState and Assignment classes

[ https://issues.apache.org/jira/browse/KAFKA-18321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-18321. --- Resolution: Fixed > Add StreamsGroupMember, MemberState and Assignment classes > ---

[jira] [Resolved] (KAFKA-18425) Remove OffsetTrackingListener

[ https://issues.apache.org/jira/browse/KAFKA-18425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18425. Resolution: Fixed trunk: https://github.com/apache/kafka/commit/aa22676c483e2e6164bd6cb67

[jira] [Created] (KAFKA-18452) Integrate share fetch batch size in share fetch

Apoorv Mittal created KAFKA-18452: - Summary: Integrate share fetch batch size in share fetch Key: KAFKA-18452 URL: https://issues.apache.org/jira/browse/KAFKA-18452 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-18397) Fix the scenario where acknowledgement callback is being called on null acknowledgements

[ https://issues.apache.org/jira/browse/KAFKA-18397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shivsundar R resolved KAFKA-18397. -- Resolution: Fixed > Fix the scenario where acknowledgement callback is being called on null >

[jira] [Resolved] (KAFKA-18428) Measure share consumers performance

[ https://issues.apache.org/jira/browse/KAFKA-18428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinav Dixit resolved KAFKA-18428. --- Resolution: Fixed > Measure share consumers performance > --

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.9 #135

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.8 #128

See

[jira] [Created] (KAFKA-18451) Flaky RemoteLogManagerTest#testRLMOpsWhenMetadataIsNotReady

Chia-Ping Tsai created KAFKA-18451: -- Summary: Flaky RemoteLogManagerTest#testRLMOpsWhenMetadataIsNotReady Key: KAFKA-18451 URL: https://issues.apache.org/jira/browse/KAFKA-18451 Project: Kafka

[jira] [Resolved] (KAFKA-18173) Remove duplicate assertFutureError

[ https://issues.apache.org/jira/browse/KAFKA-18173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18173. Fix Version/s: 4.1.0 Resolution: Fixed > Remove duplicate assertFutureError > -

[jira] [Created] (KAFKA-18450) display which role can use the config

Chia-Ping Tsai created KAFKA-18450: -- Summary: display which role can use the config Key: KAFKA-18450 URL: https://issues.apache.org/jira/browse/KAFKA-18450 Project: Kafka Issue Type: Improve

[jira] [Resolved] (KAFKA-18387) Remove UpdateMetadata and LeaderAndIsr RPC

[ https://issues.apache.org/jira/browse/KAFKA-18387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18387. Resolution: Duplicate it seems [~taijuwu] has filed PR (https://github.com/apache/kafka/pu

[jira] [Resolved] (KAFKA-18353) Remove zk config `control.plane.listener.name`

[ https://issues.apache.org/jira/browse/KAFKA-18353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18353. Resolution: Fixed trunk: https://github.com/apache/kafka/commit/0c435e3855bda58d08e280012

[jira] [Created] (KAFKA-18449) Add share-group state configs to reconfigure-server.properties

Andrew Schofield created KAFKA-18449: Summary: Add share-group state configs to reconfigure-server.properties Key: KAFKA-18449 URL: https://issues.apache.org/jira/browse/KAFKA-18449 Project: Kafka

[jira] [Created] (KAFKA-18448) Support SSL protocol with java.security.auth.login.config

PoAn Yang created KAFKA-18448: - Summary: Support SSL protocol with java.security.auth.login.config Key: KAFKA-18448 URL: https://issues.apache.org/jira/browse/KAFKA-18448 Project: Kafka Issue Typ

[jira] [Created] (KAFKA-18447) Support SASL_SSL protocol with java.security.auth.login.config

PoAn Yang created KAFKA-18447: - Summary: Support SASL_SSL protocol with java.security.auth.login.config Key: KAFKA-18447 URL: https://issues.apache.org/jira/browse/KAFKA-18447 Project: Kafka Iss

[jira] [Created] (KAFKA-18446) Remove MetadataCacheControllerNodeProvider

Chia-Ping Tsai created KAFKA-18446: -- Summary: Remove MetadataCacheControllerNodeProvider Key: KAFKA-18446 URL: https://issues.apache.org/jira/browse/KAFKA-18446 Project: Kafka Issue Type: Su

[jira] [Created] (KAFKA-18445) Remove LazyDownConversionRecords and LazyDownConversionRecordsSend

Chia-Ping Tsai created KAFKA-18445: -- Summary: Remove LazyDownConversionRecords and LazyDownConversionRecordsSend Key: KAFKA-18445 URL: https://issues.apache.org/jira/browse/KAFKA-18445 Project: Kafka

[jira] [Resolved] (KAFKA-18443) Remove ZkFourLetterWords

[ https://issues.apache.org/jira/browse/KAFKA-18443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18443. Resolution: Fixed trunk: https://github.com/apache/kafka/commit/8568157f7f022b5f2fceb9dc0

[jira] [Resolved] (KAFKA-18417) Remove controlled.shutdown.max.retries and controlled.shutdown.retry.backoff.ms

[ https://issues.apache.org/jira/browse/KAFKA-18417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18417. Fix Version/s: 4.0.0 Resolution: Fixed trunk: https://github.com/apache/kafka/comm

[jira] [Reopened] (KAFKA-18432) Remove AutoTopicCreationManager

[ https://issues.apache.org/jira/browse/KAFKA-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai reopened KAFKA-18432: > Remove AutoTopicCreationManager > --- > > Key: K

[jira] [Resolved] (KAFKA-18432) Remove AutoTopicCreationManager

[ https://issues.apache.org/jira/browse/KAFKA-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18432. Resolution: Won't Fix AutoTopicCreationManager is still used by kraft server > Remove Aut