[jira] [Created] (KAFKA-18638) Flasky test ClientIdQuotaTest.testThrottledProducerConsumer

Jimmy Wang created KAFKA-18638: -- Summary: Flasky test ClientIdQuotaTest.testThrottledProducerConsumer Key: KAFKA-18638 URL: https://issues.apache.org/jira/browse/KAFKA-18638 Project: Kafka Issu

[jira] [Resolved] (KAFKA-17963) Considering replacing LogCaptureAppender with ListAppender

[ https://issues.apache.org/jira/browse/KAFKA-17963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] TengYao Chi resolved KAFKA-17963. - Resolution: Won't Do > Considering replacing LogCaptureAppender with ListAppender >

Re: [DISCUSS] Changing which commit we build in PRs

Thanks for taking the time to explain David! That makes sense I also saw your KIP about using the merge queue so it sounds like we have a plan here On Wed, Jan 22, 2025 at 6:07 PM David Arthur wrote: > It's a good question, Sophie. The answer is not entirely obvious. > > The build cache basical

[jira] [Resolved] (KAFKA-18497) Remove config/kraft/server.properties

[ https://issues.apache.org/jira/browse/KAFKA-18497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] TengYao Chi resolved KAFKA-18497. - Resolution: Fixed > Remove config/kraft/server.properties >

Re: [DISCUSS] KIP-1126: Serialize changes to Kafka with a build queue

Hi David, Thanks for the KIP, and for your ongoing work to improve Kafka CI. Two small thoughts: 1) Today, there's a convention of waiting for a green (or at least completed) CI build before merging PRs, which includes running the full test suite. This can be relaxed on a case-by-case basis but

Re: [DISCUSS] KIP-1126: Serialize changes to Kafka with a build queue

Hey David, Is the credentials for Confluent data center different from the one used to access Apache Kafka jira? Best Regards. On Fri, 24 Jan 2025 at 03:35, David Arthur wrote: > Greetings, Kafka community! > > At long last, the GitHub Merge Queue is upon us. This is a feature that > many of u

[jira] [Created] (KAFKA-18637) Dynamic override for max.connections.per.ip is not honored

Azhar Ahmed created KAFKA-18637: --- Summary: Dynamic override for max.connections.per.ip is not honored Key: KAFKA-18637 URL: https://issues.apache.org/jira/browse/KAFKA-18637 Project: Kafka Issu

[DISCUSS] KIP-1126: Serialize changes to Kafka with a build queue

Greetings, Kafka community! At long last, the GitHub Merge Queue is upon us. This is a feature that many of us have wanted for quite a while. After many months of discussion, the excellent ASF Infra team has delivered! Since this is quite a significant change, I have written up the details as a K

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

See

Re: Requesting permissions to contribute to Apache Kafka

You should be all set. On 1/22/25 12:05 PM, Kevin Wu wrote: Hello, I am requesting permissions to contribute to Apache Kafka. Wiki ID: kw2412 Jira ID: kevinwu2412 Best, Kevin Wu

Requesting permissions to contribute to Apache Kafka

Hello, I am requesting permissions to contribute to Apache Kafka. Wiki ID: kw2412 Jira ID: kevinwu2412 Best, Kevin Wu

[jira] [Resolved] (KAFKA-18625) consumer client could get duplicated records if assigned partitions change quickly

[ https://issues.apache.org/jira/browse/KAFKA-18625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18625. - Resolution: Not A Problem > consumer client could get duplicated records if assigned partitions change

[jira] [Created] (KAFKA-18636) Javadoc failure not caught by CI

David Arthur created KAFKA-18636: Summary: Javadoc failure not caught by CI Key: KAFKA-18636 URL: https://issues.apache.org/jira/browse/KAFKA-18636 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-1124: Flexible Windows for Late Arriving Data

Thanks, Almog. Good call out about `TimeWindows` vs `TimeWindow` (yes, I am aware and was actually re-reading my previous email before sending it a few times to make sure I use the right one; it's very subtle.) For `TimeWindows` semantics are certainly well defined, and there is nothing to b

Tagged fields constraint to start from tagId: 0

Hi all, In KIP-482 , we have introduced support for optional tagged fields when the API-message supports

Re: [DISCUSS] Apache Kafka 4.0.0 release

Hey Colin -- yes, we have a blocker to bump the stable metadata versions https://issues.apache.org/jira/browse/KAFKA-18611. I can open that today or so. Justine On Thu, Jan 23, 2025 at 9:55 AM Colin McCabe wrote: > Hi David, > > We have two blockers for ELR: > > - KAFKA-18635: Re-enable the unc

Re: [DISCUSS] Apache Kafka 4.0.0 release

Hi David, We have two blockers for ELR: - KAFKA-18635: Re-enable the unclean shutdown detection when in ELR mode - KAFKA-18634: Fix ELR metadata version issues They're both pretty small and I think we can get them in in the next few days. Separately from that, is the intention to ship KIP-890 a

[jira] [Created] (KAFKA-18635) Re-enable the unclean shutdown detection when in ELR mode

Colin McCabe created KAFKA-18635: Summary: Re-enable the unclean shutdown detection when in ELR mode Key: KAFKA-18635 URL: https://issues.apache.org/jira/browse/KAFKA-18635 Project: Kafka Iss

[jira] [Created] (KAFKA-18634) Fix ELR metadata version issues

Colin McCabe created KAFKA-18634: Summary: Fix ELR metadata version issues Key: KAFKA-18634 URL: https://issues.apache.org/jira/browse/KAFKA-18634 Project: Kafka Issue Type: Bug R

[jira] [Resolved] (KAFKA-18592) Cleanup ReplicaManager

[ https://issues.apache.org/jira/browse/KAFKA-18592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18592. Fix Version/s: 4.1.0 (was: 4.0.0) Resolution: Fixed > Cleanu

[jira] [Created] (KAFKA-18633) Remove errorUnavailableEndpoints from handleTopicMetadataRequest

Chia-Ping Tsai created KAFKA-18633: -- Summary: Remove errorUnavailableEndpoints from handleTopicMetadataRequest Key: KAFKA-18633 URL: https://issues.apache.org/jira/browse/KAFKA-18633 Project: Kafka

Re: [DISCUSS] KIP-1124: Flexible Windows for Late Arriving Data

Thanks Matthias for the quick and detailed feedback! > Nit: it seems you are mixing the terms "out-of-order" and "late" and using them as synonymous, what we usually not do. M1. Ah, in my mind "late arriving" was after the window closed but potentially before grace (and "out of order" was just an

[jira] [Created] (KAFKA-18632) ShareConsumerTest multibroker tests

Sushant Mahajan created KAFKA-18632: --- Summary: ShareConsumerTest multibroker tests Key: KAFKA-18632 URL: https://issues.apache.org/jira/browse/KAFKA-18632 Project: Kafka Issue Type: Sub-tas

[jira] [Created] (KAFKA-18631) Remove ZkConfigs

Chia-Ping Tsai created KAFKA-18631: -- Summary: Remove ZkConfigs Key: KAFKA-18631 URL: https://issues.apache.org/jira/browse/KAFKA-18631 Project: Kafka Issue Type: Sub-task Reporte

Code formatter for Kafka

Hi Team, As per the readme file I could see that there are two quality analysis tools to ensure code quality. 1. Checkstyle and 2. Spotless. But, is there an official code formatter that is used in Kafka to format the code? Best, Pramithas Dhakal

[jira] [Resolved] (KAFKA-18484) More robust exception handling for new group coordinator unload

[ https://issues.apache.org/jira/browse/KAFKA-18484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-18484. - Resolution: Fixed > More robust exception handling for new group coordinator unload > --

Re: [DISCUSS] Apache Kafka 4.0.0 release

hi David Sorry for the unclear description in the previous version. I have updated the Jira ticket :) https://issues.apache.org/jira/browse/KAFKA-18627 Thanks, Chia-Ping On 2025/01/23 13:43:31 David Jacot wrote: > Hi Chia-Ping, > > Could you please extend the description of > https://issues.a

[jira] [Created] (KAFKA-18630) Clean ReplicaManagerBuilder

TengYao Chi created KAFKA-18630: --- Summary: Clean ReplicaManagerBuilder Key: KAFKA-18630 URL: https://issues.apache.org/jira/browse/KAFKA-18630 Project: Kafka Issue Type: Sub-task Re

Re: [DISCUSS] Apache Kafka 4.0.0 release

Hi Chia-Ping, Could you please extend the description of https://issues.apache.org/jira/browse/KAFKA-18627 to explain why we need to do this? It is hard to understand the need in the current state. Hi Luke, I will take a look at https://issues.apache.org/jira/browse/KAFKA-18230. Best, David On

[jira] [Resolved] (KAFKA-17699) Set default test quorum to kraft

[ https://issues.apache.org/jira/browse/KAFKA-17699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17699. Resolution: Duplicate there is no quorum=zk in test > Set default test quorum to kraft >

[jira] [Created] (KAFKA-18629) DeleteShareGroups impl

Sushant Mahajan created KAFKA-18629: --- Summary: DeleteShareGroups impl Key: KAFKA-18629 URL: https://issues.apache.org/jira/browse/KAFKA-18629 Project: Kafka Issue Type: Sub-task

Re: [DISCUSS] KIP-1124: Flexible Windows for Late Arriving Data

Interesting KIP. It's a known problem, and the proposed solution make sense to me. Nit: it seems you are mixing the terms "out-of-order" and "late" and using them as synonymous, what we usually not do. "Out-of-order" is the more generic term, while "late" means after the grace period (hence,