[jira] [Resolved] (KAFKA-18791) Set default commit message to PR title + body

[ https://issues.apache.org/jira/browse/KAFKA-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Arthur resolved KAFKA-18791. -- Resolution: Fixed > Set default commit message to PR title + body > --

[jira] [Created] (KAFKA-18835) Remove redundant kraft quorum param from consumer integration tests

Lianet Magrans created KAFKA-18835: -- Summary: Remove redundant kraft quorum param from consumer integration tests Key: KAFKA-18835 URL: https://issues.apache.org/jira/browse/KAFKA-18835 Project: Kafk

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

See

[jira] [Resolved] (KAFKA-18579) Add TransactionAbortableException instruction in docs

[ https://issues.apache.org/jira/browse/KAFKA-18579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaushik Raina resolved KAFKA-18579. --- Resolution: Fixed > Add TransactionAbortableException instruction in docs >

[jira] [Resolved] (KAFKA-18835) Remove redundant kraft quorum param from consumer integration tests

[ https://issues.apache.org/jira/browse/KAFKA-18835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lianet Magrans resolved KAFKA-18835. Resolution: Duplicate > Remove redundant kraft quorum param from consumer integration test

[jira] [Resolved] (KAFKA-18833) Infinite loop on authenticcation error with AWS MSK AIM

[ https://issues.apache.org/jira/browse/KAFKA-18833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-18833. - Resolution: Invalid > Infinite loop on authenticcation error with AWS MSK AIM >

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

Hi Kevin, Thanks for the KIP. I notice that you have some metrics that reflect times here, such as LongestPendingStartupTimeMs, LongestPendingControlledShudownTimeMs, etc. I think this may be difficult to do with complete accuracy because we don't include times in the metadata log events for r

[jira] [Created] (KAFKA-18836) Make ConsumerGroupMetadata an interface

Matthias J. Sax created KAFKA-18836: --- Summary: Make ConsumerGroupMetadata an interface Key: KAFKA-18836 URL: https://issues.apache.org/jira/browse/KAFKA-18836 Project: Kafka Issue Type: Imp

Default PR commit message template

Hey folks, just wanted to let you all know we have made a GitHub configuration change for our PRs. If you’ve ever wondered why the default commit message in GitHub PRs seems to be kind of weird and arbitrary, you are not alone! Turns out the “default” commit message for PRs is rather unintuitive a

Re: Default PR commit message template

Big thanks to David and ASF infra! Best, Chia-Ping > David Arthur 於 2025年2月20日 凌晨4:00 寫道： > > Hey folks, just wanted to let you all know we have made a GitHub > configuration change for our PRs. > > If you’ve ever wondered why the default commit message in GitHub PRs seems > to be kind of w

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

Hi Lianet, Thank you for your feedback! Yes, the current KIP focuses solely on the client upgrade for 4.x. I have updated the title accordingly and also included the KS upgrade link in the KIP. Thanks again! Best regards, Kuan-Po On 2025/02/19 16:59:25 "Lianet M." wrote: > Hello all, sorry a

[jira] [Resolved] (KAFKA-17420) Fix flaky StreamThreadTest.tearDown

[ https://issues.apache.org/jira/browse/KAFKA-17420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17420. Resolution: Duplicate agree to close this ticket. loop it 500times on my local. all pass

[jira] [Resolved] (KAFKA-18822) Fail test LoggingResourceTest#testSetLevelDefaultScope, testSetLevelInvalidScope

[ https://issues.apache.org/jira/browse/KAFKA-18822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18822. Resolution: Duplicate see KAFKA-18834 > Fail test LoggingResourceTest#testSetLevelDefault

[jira] [Resolved] (KAFKA-16918) TestUtils#assertFutureThrows should use future.get with timeout

[ https://issues.apache.org/jira/browse/KAFKA-16918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-16918. Fix Version/s: 4.1.0 Resolution: Fixed > TestUtils#assertFutureThrows should use fu

[jira] [Created] (KAFKA-18829) Can't use explicit ack when poll returns an empty batch

Gunnar Morling created KAFKA-18829: -- Summary: Can't use explicit ack when poll returns an empty batch Key: KAFKA-18829 URL: https://issues.apache.org/jira/browse/KAFKA-18829 Project: Kafka I

[jira] [Resolved] (KAFKA-18198) Disallow piggyback acknowledgments on initial ShareFetchRequest.

[ https://issues.apache.org/jira/browse/KAFKA-18198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18198. -- Fix Version/s: 4.1.0 Resolution: Fixed > Disallow piggyback acknowledgments on

[jira] [Created] (KAFKA-18830) Enable parallel processing for transformation chain

Padmaprasad Aithal created KAFKA-18830: -- Summary: Enable parallel processing for transformation chain Key: KAFKA-18830 URL: https://issues.apache.org/jira/browse/KAFKA-18830 Project: Kafka

[jira] [Resolved] (KAFKA-18601) Assume a baseline of 3.3 for server protocol versions

[ https://issues.apache.org/jira/browse/KAFKA-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-18601. - Resolution: Fixed > Assume a baseline of 3.3 for server protocol versions >

[jira] [Created] (KAFKA-18832) ShareFetch behaviour seems incorrect when MaxBytes is less than record d

Andrew Schofield created KAFKA-18832: Summary: ShareFetch behaviour seems incorrect when MaxBytes is less than record d Key: KAFKA-18832 URL: https://issues.apache.org/jira/browse/KAFKA-18832 Proj

[jira] [Created] (KAFKA-18833) Infinite loop on authenticcation error with AWS MSK AIM

Sergey Kadaner created KAFKA-18833: -- Summary: Infinite loop on authenticcation error with AWS MSK AIM Key: KAFKA-18833 URL: https://issues.apache.org/jira/browse/KAFKA-18833 Project: Kafka I

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

Hello all, sorry a bit late, just minor comments on this one: - Should we clarify in the title or at the beginning of the KIP that it is proposing a client upgrade path for 4.x? The broader considerations for upgrades discussed in this thread will be tackled separately (seems we all agree). - The

[jira] [Created] (KAFKA-18831) Document the behavior changes of adjusting logger level after migrating to log4j2

Chia-Ping Tsai created KAFKA-18831: -- Summary: Document the behavior changes of adjusting logger level after migrating to log4j2 Key: KAFKA-18831 URL: https://issues.apache.org/jira/browse/KAFKA-18831

Re: [DISCUSS] Apache Kafka 4.0.0 release

hi David, I've filed a new blocker (KAFKA-18831) to address the Log4j 2 behavior changes. We've identified the root cause and are preparing a PR, so it should be fixed this week. Best, Chia-Ping On 2025/01/23 07:15:45 Chia-Ping Tsai wrote: > hi David > > Could you please take a look at > htt

[jira] [Created] (KAFKA-18834) Fix LoggingResourceTest#testSetLevelDefaultScope

Chia-Ping Tsai created KAFKA-18834: -- Summary: Fix LoggingResourceTest#testSetLevelDefaultScope Key: KAFKA-18834 URL: https://issues.apache.org/jira/browse/KAFKA-18834 Project: Kafka Issue Ty