Re: [VOTE] KIP-1124: Providing a clear Kafka Client upgrade path

Hi, The vote should remain open for 72 hours. Given that the KIP discussion only really converted yesterday, I think we should count the 72 hours from that point forward. Ismael On Wed, Mar 5, 2025, 6:40 PM Kuan Po Tseng wrote: > Thanks everyone for voting and feedback. > > The vote has passed

[jira] [Reopened] (KAFKA-18246) Fix ConnectRestApiTest.test_rest_api by adding multiversioning configs

[ https://issues.apache.org/jira/browse/KAFKA-18246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai reopened KAFKA-18246: > Fix ConnectRestApiTest.test_rest_api by adding multiversioning configs > ---

Re: [DISCUSS] KIP-896: Remove old client protocol API versions in Kafka 4.0

Hi Jun, Thanks for uncovering this issue. Thinking through it, I think there are two hard constraints: 1. We do not want 4.0 brokers to break recent releases of widely deployed clients. 2. We do not want 4.0 clients to break with supported broker versions (2.1 and newer). The issue you raised wo

Re: [VOTE] KIP-1124: Providing a clear Kafka Client upgrade path

Thanks everyone for voting and feedback. The vote has passed with 4 binding votes (Matthias, Chia-Ping, David and Bruno). Best, Kuan-Po Tseng On 2025/03/05 09:30:55 Bruno Cadonna wrote: > Hi, > > +1 (binding) > > Thanks for the KIP, > Bruno > > On 05.03.25 09:49, David Jacot wrote: > > +1 (bi

[jira] [Created] (KAFKA-18927) Remove LATEST_0_11, LATEST_1_0, LATEST_1_1, LATEST_2_0

Chia-Ping Tsai created KAFKA-18927: -- Summary: Remove LATEST_0_11, LATEST_1_0, LATEST_1_1,LATEST_2_0 Key: KAFKA-18927 URL: https://issues.apache.org/jira/browse/KAFKA-18927 Project: Kafka

Re: [VOTE] 4.0.0 RC1

Hi Jun, Thanks for letting me know. I agree that this is nothing that we need to sort out before 4.0 goes out. I suggest you file a blocker to track it. Best, David On Wed, Mar 5, 2025 at 7:22 PM Jun Rao wrote: > Hi, David, > > Thanks for preparing RC1. > > The following is a potential 4.0.0 b

[jira] [Created] (KAFKA-18928) Support to dynamically change config for specific controller

Chia-Ping Tsai created KAFKA-18928: -- Summary: Support to dynamically change config for specific controller Key: KAFKA-18928 URL: https://issues.apache.org/jira/browse/KAFKA-18928 Project: Kafka

Re: Protected Branches and Required Checks

The up-to-date requirement should not be there (for the reasons you mentioned). There was a bug with the Infra asf.yaml parser, so Infra manually removed the up-to-date requirement. If the checks all pass and the PR is approved, it should be mergeable up-to-date or not. Let me know if this isn’t t

Re: Protected Branches and Required Checks

Ok looks like Infra’s manual GitHub config change got undone. I see that this PR https://github.com/apache/kafka/pull/19120 is approved, but can't be merged :( I filed https://issues.apache.org/jira/browse/INFRA-26601, hopefully someone gets to it soon. On Wed, Mar 5, 2025 at 23:19 David Arth

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

Thanks for the KIP! The proposal here sounds like the right direction to go in for me, but I'll be interested to hear what others think. I'm wondering if we should offer additional StreamsBuilder & Topology constructors that accept a plain config map (or Properties) alongside the StreamsConfig con

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

See

Re: Protected Branches and Required Checks

hi David Thank you for this protection, and I fully agree that we need to avoid exceptional merges as much as possible. For another, It seems we also require PRs to be up-to-date, which is good. However, the side effect is cache misses. I recall you've done a lot of work on improving the cache, s

Re: [VOTE] KIP-1124: Providing a clear Kafka Client upgrade path

I meant converged (instead of converted). On Wed, Mar 5, 2025, 9:22 PM Ismael Juma wrote: > Hi, > > The vote should remain open for 72 hours. Given that the KIP discussion > only really converted yesterday, I think we should count the 72 hours from > that point forward. > > Ismael > > On Wed, Ma

Re: [VOTE] KIP-1124: Providing a clear Kafka Client upgrade path

+1 (binding). Thanks for pushing this forward! On Wed, Mar 5, 2025 at 8:30 AM Chia-Ping Tsai wrote: > +1 (binding) > > On 2025/02/12 14:49:37 Kuan Po Tseng wrote: > > Hello, > > I'd like to initiate a vote on KIP-1124, which aims to provide a clear > > upgrade path for Kafka clients. This propos

[jira] [Resolved] (KAFKA-12903) Replace producer state entry with auto-generated protocol

[ https://issues.apache.org/jira/browse/KAFKA-12903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-12903. - Resolution: Duplicate Already fixed in KAFKA-17056 > Replace producer state entry with auto-gen

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

Hi Matthias, You're right and I agree with your comments. Paweł—I'm happy with the KIP given Matthias’ points. Thanks, Kirk On Tue, Mar 4, 2025, at 12:20 PM, Matthias J. Sax wrote: > Hi, > > I think it should be sufficient to just state in the JavaDocs of the new > interface, that the interfa

[jira] [Resolved] (KAFKA-18882) Remove BaseKey, TxnKey, and UnknownKey

[ https://issues.apache.org/jira/browse/KAFKA-18882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18882. Fix Version/s: 4.1.0 Resolution: Fixed > Remove BaseKey, TxnKey, and UnknownKey > -

[jira] [Resolved] (KAFKA-18804) Remove slf4j warning when using tool script.

[ https://issues.apache.org/jira/browse/KAFKA-18804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18804. Fix Version/s: 4.1.0 Resolution: Fixed > Remove slf4j warning when using tool scrip

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

Hi, Thanks for the KIP. Why did we reject the alternative where the constructor is unavailable to external users? Ismael On Tue, Feb 25, 2025 at 8:27 AM Paweł Szymczyk wrote: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1136%3A+Make+ConsumerGroupMetadata+an+interface > > -- > Pozd

Re: [VOTE] 4.0.0 RC1

Hi, David, Thanks for preparing RC1. The following is a potential 4.0.0 blocker since it may involve a protocol change. https://github.com/apache/kafka/pull/18726#discussion_r1972525165 Thanks, Jun On Wed, Mar 5, 2025 at 7:38 AM David Jacot wrote: > We still have two documentation blockers:

[jira] [Resolved] (KAFKA-18919) Clarify that KafkaPrincipalBuilder classes must also implement KafkaPrincipalSerde

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

[jira] [Created] (KAFKA-18925) Add streams groups support in `Admin.listGroups`.

Lucas Brutschy created KAFKA-18925: -- Summary: Add streams groups support in `Admin.listGroups`. Key: KAFKA-18925 URL: https://issues.apache.org/jira/browse/KAFKA-18925 Project: Kafka Issue T

[jira] [Resolved] (KAFKA-18887) Implement Admin API extensions beyond list/describe group (delete group, offset-related APIs)

[ https://issues.apache.org/jira/browse/KAFKA-18887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Brutschy resolved KAFKA-18887. Resolution: Fixed > Implement Admin API extensions beyond list/describe group (delete grou

Re: [VOTE] KIP-1124: Providing a clear Kafka Client upgrade path

Hi, +1 (binding) Thanks for the KIP, Bruno On 05.03.25 09:49, David Jacot wrote: +1 (binding). Thanks for pushing this forward! On Wed, Mar 5, 2025 at 8:30 AM Chia-Ping Tsai wrote: +1 (binding) On 2025/02/12 14:49:37 Kuan Po Tseng wrote: Hello, I'd like to initiate a vote on KIP-1124, wh

[jira] [Created] (KAFKA-18924) Running the storage module tests produces a storage/storage.log file

Mickael Maison created KAFKA-18924: -- Summary: Running the storage module tests produces a storage/storage.log file Key: KAFKA-18924 URL: https://issues.apache.org/jira/browse/KAFKA-18924 Project: Kaf

[VOTE] 4.0.0 RC1

Hello Kafka users, developers and client-developers, This is the second candidate for release of Apache Kafka 4.0.0. - This is the first release without Apache Zookeeper - The Next Generation of the Consumer Rebalance Protocol is Generally Available - The Transactions Server-Side Defense (Phase 2

Re: [VOTE] 4.0.0 RC1

We still have two documentation blockers: * https://issues.apache.org/jira/browse/KAFKA-18074 * https://issues.apache.org/jira/browse/KAFKA-18422 They should be resolved by the end of the week. I will update the documentation when they are merged. Best, David On Wed, Mar 5, 2025 at 4:35 PM David

[jira] [Created] (KAFKA-18926) `KafkaPrincipalBuilder` should extend `KafkaPrincipalSerde`

Chia-Ping Tsai created KAFKA-18926: -- Summary: `KafkaPrincipalBuilder` should extend `KafkaPrincipalSerde` Key: KAFKA-18926 URL: https://issues.apache.org/jira/browse/KAFKA-18926 Project: Kafka

[jira] [Resolved] (KAFKA-14121) AlterPartitionReassignments API should allow callers to specify the option of preserving the replication factor

[ https://issues.apache.org/jira/browse/KAFKA-14121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuan Po Tseng resolved KAFKA-14121. --- Resolution: Fixed > AlterPartitionReassignments API should allow callers to specify the opti

Re: [DISCISS] KIP-860: Add client-provided option to guard against unintentional replication factor change during partition reassignments

Hi everyone, Just a quick update—I’ve made some adjustments to the KIP: - Changed allowReplicationFactorChange from Boolean to boolean. - Adopted the fluent pattern in AlterPartitionReassignmentsOptions. Also, the PR has been merged into trunk, targeting version 4.1.0. Thanks again for your supp

Protected Branches and Required Checks

We had a hiccup today where a PR was merged due to a false positive "All checks have passed" message in the UI. This message was displayed because the labelling workflows had run and were successful. So, really the message was correct -- all checks that had been run were successful. The problem was

Re: [DISCUSS] KIP-1131: Controller-side monitoring for broker shutdown and startup

On Thu, Feb 27, 2025, at 12:19, Kevin Wu wrote: >> >> I guess my concern is that the time-based metrics would reset to 0 on >> every failover (if I understand the proposed implementation correctly). >> That seems likely to create confusion. > > Yeah that makes sense to me. I'm fine with moving towa

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

Reversing the question. What is the problem with using an interface? It seem, and interface would provide the cleanest way to separate public and internal things? Or maybe I misunderstand what you propose? We can for sure not have a `private` constructor. We can also not have "package private"

Confluence permission for KIP

Hi, I am new to Apache Kafka. Could someone give me permission of Kafka Confluence ( https://cwiki.apache.org/confluence/display/kafka ) for writing KIP? My confluence username is "johnny94"

Re: Confluence permission for KIP

Hi Johnny, I can't seem to locate your username in https://cwiki.apache.org/confluence/display/kafka. Can you confirm it? Also, IIRC, you still need to sign up for a user account in the Kafka Confluence space even if you have a general Confluence account (but I could be wrong here). Thanks for yo