[jira] [Resolved] (KAFKA-18855) MemoryRecords should have slice API

[ https://issues.apache.org/jira/browse/KAFKA-18855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18855. Fix Version/s: 4.1.0 Resolution: Fixed > MemoryRecords should have slice API >

Re: [DISCUSS] KIP-1153: Kafka Streams `CloseOptions` should not have a public constructor

> One more nit: we should remove the getters. There are useless. -- In Kafka Streams, we follow the pattern to have a (non-public) sub-class `CloseOptionsInternal` which would add the necessary getters KS runtime needs. IIRC, we had a similar discussion regarding "internal" classes previously. To

Re: [DISCUSS] KIP-1153: Kafka Streams `CloseOptions` should not have a public constructor

Thanks for updating the KIP. One more nit: we should remove the getters. There are useless. -- In Kafka Streams, we follow the pattern to have a (non-public) sub-class `CloseOptionsInternal` which would add the necessary getters KS runtime needs. Cf https://github.com/apache/kafka/blob/trun

RE: Re: [DISCUSS] KIP-1150 Diskless Topics

Hi Ivan, KIP-E: Producer Rack Awareness seems to be a subset of KIP-1123. I don’t know the process but maybe it’s worth linking somehow? (I hope this reply lands under the correct message, I haven’t used mailing lists in a decade or two) Kind regards, Jan On 2025/04/23 12:04:45 Ivan Yurchenko

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

See

Re: [DISCUSS] KIP-1176: Tiered Storage for Active Log Segment

Hi Henry, Thank you for your detailed reply. The answer makes sense to me, and you're right, KIP-1176 has a clear and specific scope and is expected to have a quick path to implement it. I also want to discuss the metadata management of WAL log segments. Is an internal topic necessary for managin

Re: [VOTE] KIP-1166: Improve high-watermark replication

Hi Jose, Thanks for the KIP. +1 (binding) best, Colin On Wed, May 7, 2025, at 11:02, David Arthur wrote: > Thanks José, > > +1 binding > > -David A > > On Mon, May 5, 2025 at 4:47 PM Alyssa Huang > wrote: > >> Hey Jose, >> >> KIP looks good to me as well! >> >> On Mon, May 5, 2025 at 10:08 AM

[VOTE] KIP-1155: Metadata Version Downgrades

Hi all, I'd like to start a vote on KIP-1155: Metadata Version Downgrades. https://cwiki.apache.org/confluence/display/KAFKA/KIP-1155%3A+Metadata+Version+Downgrades The discussion thread is here: https://lists.apache.org/thread/cwhkf26np3kjt33yhlsvp3k3jf7ofgf3 best, Colin

Re: [DISCUSS] Apache Kafka 4.1.0 release

Hi Mickael, Can we add KIP-1139 (https://cwiki.apache.org/confluence/x/uIxEF) to the 4.1.0 "Planned KIP Content" list? It was approved yesterday. Thanks, Kirk On Wed, Mar 19, 2025, at 4:58 AM, Mickael Maison wrote: > Hi, > > I'd like to volunteer to be the release manager for the Apache Kafka

Re: [DISCUSS] KIP-1180: Add a generic feature level metric

Hi, Kevin, Thanks for the KIP. A few comments below. 1. For completeness, there is another feature streams.version. 2. "The default value of this metric should be the default value of the feature." This metric reports the finalized level for each feature, right? If a feature is not set, should t

[jira] [Resolved] (KAFKA-19212) Fix ElectionWasClean bug when partition reassignment completes

[ https://issues.apache.org/jira/browse/KAFKA-19212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-19212. - Resolution: Fixed merged the PR to trunk > Fix ElectionWasClean bug when partition reassignment complet

Re: [DISCUSS] KIP-1180: Add a generic feature level metric

Hi Kevin, Thanks for the changes. For the "Rejected Alternatives" section you can state why using "kafka-feature describe" is not sufficient. Thanks, -- -José

[jira] [Created] (KAFKA-19254) Add generic feature level metric

Kevin Wu created KAFKA-19254: Summary: Add generic feature level metric Key: KAFKA-19254 URL: https://issues.apache.org/jira/browse/KAFKA-19254 Project: Kafka Issue Type: New Feature

Re: [DISCUSS] KIP-1180: Add a generic feature level metric

Hey Jose, Thanks for the response. Yeah, the new metric should expose metadata.version as well. Let me update the KIP to reflect that. Thanks, Kevin Wu On Wed, May 7, 2025 at 2:54 PM Kevin Wu wrote: > Hello all, > > I wrote a KIP to add a generic feature level metric. > Here's the link: > http

Re: [DISCUSS] KIP-1180: Add a generic feature level metric

Hi Kevin, Thanks for the improvement and discussion. The "Monitoring" section says "Add a metric for each production feature (i.e. kraft.version , transaction.version , group.version , eligible.leader.replicas.version , and share.version )." You mentioned that the metadata version is already expo

[DISCUSS] KIP-1180: Add a generic feature level metric

Hello all, I wrote a KIP to add a generic feature level metric. Here's the link: https://cwiki.apache.org/confluence/display/KAFKA/KIP-1180%3A+Add+a+generic+feature+level+metric Thanks, Kevin Wu

Re: [VOTE] KIP-1166: Improve high-watermark replication

Thanks José, +1 binding -David A On Mon, May 5, 2025 at 4:47 PM Alyssa Huang wrote: > Hey Jose, > > KIP looks good to me as well! > > On Mon, May 5, 2025 at 10:08 AM Jun Rao wrote: > > > Hi, Jose, > > > > Thanks for the KIP. +1 > > > > Jun > > > > On Fri, May 2, 2025 at 8:42 AM José Armando G

Re: [DISCUSS] KIP-1176: Tiered Storage for Active Log Segment

Xinyu, Thanks for your time reading the KIP and detailed comments.  We are honored to have technical leaders from AutoMQ to look at our work. Please see my answers below inline. On Tuesday, May 6, 2025 at 08:37:22 PM PDT, Xinyu Zhou wrote: Hi Henry and Tom, I've read the entire KIP-1

RE: [DISCUSS] KIP-1121: Compression acceleration in Kafka

Hi Greg, 2, 10 I figured a way to not expose any of these internal classes to the public API. I added a new interface in the place of BufferSupplier. 7. No, CompressionService#isAvailable returning false does not currently cause a ConfigException, it would cause a fall-back to the base implement

[VOTE] KIP-1162: Redesign ClientQuotaCallback#updateClusterMetadata

Hello everyone, I’d like to initiate a vote on KIP-1162. Thank you for your attention! KIP: https://cwiki.apache.org/confluence/x/zInoF Discussion thread: https://lists.apache.org/thread/9l6m1scv765ohbwjkwq5sotjcdjzjp4q Best regards, Kuan-Po Tseng

[jira] [Created] (KAFKA-19253) Implement CCloud metadata version handling correctly for enabling QfK feature

Abhinav Dixit created KAFKA-19253: - Summary: Implement CCloud metadata version handling correctly for enabling QfK feature Key: KAFKA-19253 URL: https://issues.apache.org/jira/browse/KAFKA-19253 Proje

[jira] [Resolved] (KAFKA-19215) Handle share partition fetch lock cleanly in DelayedShareFetch to avoid a member incorrectly releasing a share partition's fetch lock

[ https://issues.apache.org/jira/browse/KAFKA-19215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-19215. --- Fix Version/s: 4.1.0 Resolution: Fixed > Handle share partition fetch lock cleanly in

Re: [DISCUSS] KIP-1100: Consider renaming org.apache.kafka.server:type=AssignmentsManager

Hi all, This KIP now encompasses the work outlined in the following Jira tickets: - KAFKA-17876 - KAFKA-19150 Both tickets aim to deprecate and update incorrectly named metrics to align with the standard kafka. naming convention. Best Regards, Jiunn-Yang > 黃竣陽 於 2025年5月5日 晚上7:26 寫道： > > H

Re: Request to edit permission on Kafka Confluence space

Hi David, Do you have a Confluence account? If so, can you share your id so we can grant you the right permissions? Best, On Wed, May 7, 2025 at 4:32 PM david kjerrumgaard wrote: > Hello all, > > I am trying to create a KIP but lack the permissions to do so. Can someone > please help me with th

Request to edit permission on Kafka Confluence space

Hello all, I am trying to create a KIP but lack the permissions to do so. Can someone please help me with this? Regards, David Kjerrumgaard

[jira] [Created] (KAFKA-19252) Support broker and controller restarts in testkit

David Arthur created KAFKA-19252: Summary: Support broker and controller restarts in testkit Key: KAFKA-19252 URL: https://issues.apache.org/jira/browse/KAFKA-19252 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-19251) Resolve the flaky test ShareConsumerTest.testMultipleConsumersInGroupConcurrentConsumption

Chirag Wadhwa created KAFKA-19251: - Summary: Resolve the flaky test ShareConsumerTest.testMultipleConsumersInGroupConcurrentConsumption Key: KAFKA-19251 URL: https://issues.apache.org/jira/browse/KAFKA-19251

[jira] [Resolved] (KAFKA-18796) Fix flaky test testAcquisitionLockOnOffsetWithWriteShareGroupStateFailure

[ https://issues.apache.org/jira/browse/KAFKA-18796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinav Dixit resolved KAFKA-18796. --- Fix Version/s: 4.1.0 Resolution: Fixed > Fix flaky test testAcquisitionLockOnOffsetWi

[jira] [Resolved] (KAFKA-19241) Reuse the same socket on subsequent share requests in ShareFetchAcknowledgeRequestTest

[ https://issues.apache.org/jira/browse/KAFKA-19241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-19241. --- Fix Version/s: 4.1.0 Resolution: Fixed > Reuse the same socket on subsequent share re

[jira] [Created] (KAFKA-19250) Validate abortTransactions should not return abortable exception

Kaushik Raina created KAFKA-19250: - Summary: Validate abortTransactions should not return abortable exception Key: KAFKA-19250 URL: https://issues.apache.org/jira/browse/KAFKA-19250 Project: Kafka