[jira] [Resolved] (KAFKA-18576) Convert ConfigType to Enum

[ https://issues.apache.org/jira/browse/KAFKA-18576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] TengYao Chi resolved KAFKA-18576. - Reviewer: Chia-Ping Tsai Resolution: Fixed > Convert ConfigType to Enum >

Re: [DISCUSS] KIP-1136: Make ConsumerGroupMetadata an interface

hi All, > Matthias J. Sax 於 2025年3月5日 凌晨4:20 寫道： > > To me, the main thing is really, that currently user can call `new` what > makes it easy to do thing wrong. If we change it to an interface, users > cannot call `new`, and if the interface says "do not implement me", it should > hopefully t

[DISCUSS] KIP-1148: Remove log.cleaner.enable configuration

Hello everyone, I want to start a discussion thread on KIP-1148 , which proposes removing the `log.cleaner.enable` configuration. Please take a look and let me know what you think. I would appreciate any suggestions and feedback. Best regards, TengYao

[jira] [Created] (KAFKA-19036) Rewrite LogAppendTimeTest and move it to server module

PoAn Yang created KAFKA-19036: - Summary: Rewrite LogAppendTimeTest and move it to server module Key: KAFKA-19036 URL: https://issues.apache.org/jira/browse/KAFKA-19036 Project: Kafka Issue Type:

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

See

Re: [DISCUSS] KIP-1136: Make ConsumerGroupMetadata an interface

Hi Paweł, We can't change the existing (public) constructors to private in 4.1 as that would break users. Yes, we can argue that users shouldn't be instantiating the ConsumerGroupMetadata in the first place, but as of 4.0 those constructors are part of the published API. For 4.1, at most we co

Re: [DISCUSS] KIP-1143: Deprecated Optional and return String from public Endpoint#listenerName

Hi PoAn, Thanks for the KIP. I have two uneducated questions based regarding expected usage by the client layer: KT1. Can you elaborate on the statement from the Motivation section, "However, we don't fully utilized this approach?" Is "we" the Kafka project's internals, or the community? KT

Re: [DISCUSS] KIP-1140: Avoid to return null value in Map from public api of consumer

Hi Jiunn-Yang, Regardless of what form the KIP takes and when it's implemented, near term it would be good to see a PR with some of these null edge cases clearly spelled out in the JavaDoc. Then, once the KIP is accepted, those comments could be updated with the intended future changes. Thanks

[jira] [Created] (KAFKA-19035) Ensure DLQ can be tested using TTD

Matthias J. Sax created KAFKA-19035: --- Summary: Ensure DLQ can be tested using TTD Key: KAFKA-19035 URL: https://issues.apache.org/jira/browse/KAFKA-19035 Project: Kafka Issue Type: Sub-task

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

Hi, I agree with the KIP, it makes sense to reduce the number of ways the configs get passed. I agree with Sophie that it doesn't make sense to rewrite the topology compilation just to delay reading the configs. The question StreamsConfig vs. Map/Properties is less clear-cut to me. The immutabili

Re: [VOTE] KIP-1064 - Upgrade slf4j to 2.x

Thank you for the response, Chia-Ping Tsai. The sl4j and System.Logger APIs are very similar and lightweight. Is there any particular API or functionality missing from System.Logger? Yes, all logging libraries/providers support System.Logger. Libraries like log4j2, which is what Kafka defaults t

Re: [DISCUSS] KIP-1101: Trigger rebalance on rack topology changes

Hi PoAn, Thanks for the clarification! Best, Jeff On Mon, Mar 24, 2025 at 11:43 AM PoAn Yang wrote: > Hi Jeff, > > Thanks for the review. > > JK01. Yes, we already maintain `groupByTopics` data structure in the > coordinator. If a group leaves, > it checks whether a topic is subscribed by any

Re: [VOTE] KIP-1064 - Upgrade slf4j to 2.x

Why not use the System.Logger logging facade built-into JDK9+ instead of the third party SLF4J alternative? System.Logger seems the simpler option. I understand that when the Kafka project was supporting Java 8, System.Logger was not an option, but now the Kafka project requires JDK 11+. https://d

[jira] [Created] (KAFKA-19034) Rewrite RemoteTopicCrudTest by ClusterTest and move it to storage module

Chia-Ping Tsai created KAFKA-19034: -- Summary: Rewrite RemoteTopicCrudTest by ClusterTest and move it to storage module Key: KAFKA-19034 URL: https://issues.apache.org/jira/browse/KAFKA-19034 Project:

Re: [DISCUSS] KIP-1136: Make ConsumerGroupMetadata an interface

mj...@apache.org any update on that? Can we release it in 4.1.0? pt., 7 mar 2025 o 09:08 Paweł Szymczyk napisał(a): > mj...@apache.org the main point is that this class is a regular data > structure, there is no way to give an alternative implementation which is > the purpose of interface in Ja

[jira] [Resolved] (KAFKA-19033) FindCoordinator API always return COORDINATOR_NOT_AVAILABLE for CoordinatorType.SHARE

[ https://issues.apache.org/jira/browse/KAFKA-19033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-19033. Resolution: Duplicate > FindCoordinator API always return COORDINATOR_NOT_AVAILABLE for >

[jira] [Created] (KAFKA-19033) FindCoordinator API always return COORDINATOR_NOT_AVAILABLE for CoordinatorType.SHARE

Chia-Ping Tsai created KAFKA-19033: -- Summary: FindCoordinator API always return COORDINATOR_NOT_AVAILABLE for CoordinatorType.SHARE Key: KAFKA-19033 URL: https://issues.apache.org/jira/browse/KAFKA-19033

Re: [DISCUSS] KIP-1101: Trigger rebalance on rack topology changes

Hi Jeff, Thanks for the review. JK01. Yes, we already maintain `groupByTopics` data structure in the coordinator. If a group leaves, it checks whether a topic is subscribed by any group. If it’s not, remove topic hash from the cache. Please check the sample implementation about GroupMetadataMa

Re: [DISCUSS] KIP-1143: Deprecated Optional and return String from public Endpoint#listenerName

hi PoAn Have you consider aligning the naming of `RaftVoterEndpoint`? i.e deprecate `name()` and add `listener()` for consistency. Best, Chia-Ping On 2025/03/16 12:52:42 PoAn Yang wrote: > Hi all, > > I would like to start a discussion thread on KIP-1143. > > This KIP removes redundant org.ap

[jira] [Resolved] (KAFKA-19031) Ensure brokers do not return null records in ShareFetchResponse

[ https://issues.apache.org/jira/browse/KAFKA-19031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] TengYao Chi resolved KAFKA-19031. - Resolution: Duplicate It seems that this is a duplicate. I will close this one. :) > Ensure bro

[DISCUSS] KIP-1149 Helm Chart for Apache Kafka

Hi All, I've opened a new KIP-1149: Helm Chart for Apache Kafka with the proposal to have an official Helm chart to deploy Apache Kafka to Kubernetes. The initial Jira ticket (KAFKA-6416

Re: Requesting permission to contribute to Apache Kafka

Stephen, You should be good now. Regards, Bill On Mon, Mar 24, 2025 at 8:30 AM Stephen Askew wrote: > Hello, > > As per the instructions at Kafka Improvement Proposals - Apache Kafka - > Apache Software Foundation< > https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals

Requesting permission to contribute to Apache Kafka

Hello, As per the instructions at Kafka Improvement Proposals - Apache Kafka - Apache Software Foundation, I'm requesting permission to contribute to Apache Kafka. My Jira id and Wiki id are both askew The reason f

Re: [DISCUSS] KIP-1110: Metadata of sensitive configuration

Bump this thread to seek for feedback or suggestions. Thanks. Luke On Tue, Nov 26, 2024 at 4:30 PM Luke Chen wrote: > Hi Federico, > > Thanks for the comment. > I've updated the field name to LastUpdateTimestampMs. > > Luke > > On Tue, Nov 19, 2024 at 7:21 PM Federico Valeri > wrote: > >> Hi L

[DISCUSS] Apache Kafka 3.9.1 release

Hi all, I'll be the release manager for a bug fix release of the 3.9.1 release. Here you have the release plan for 3.9.1: https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.1 I'm aiming to have the first release candidate *by the mid of April* since there are still some opening i

Re: [VOTE] KIP-1123: Rack-aware partitioning for Kafka Producer

+1 (non-binding) On Sat, Mar 22, 2025 at 12:32 PM Ivan Yurchenko wrote: > Hi! > > As there's no more comments regarding KIP-1123 [1], I'd like to put it to > a vote. > > Best regards, > Ivan > > [1] > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1123:+Rack-aware+partitioning+for+Kafka+P