Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #1970

See Changes: -- [...truncated 386274 lines...] Gradle Test Run :streams:integrationTest > Gradle Test Executor 181 > TableTableJoinIntegrationTest > [caching enabled = fa

[jira] [Created] (KAFKA-15146) Flaky test ConsumerBounceTest.testConsumptionWithBrokerFailures

Divij Vaidya created KAFKA-15146: Summary: Flaky test ConsumerBounceTest.testConsumptionWithBrokerFailures Key: KAFKA-15146 URL: https://issues.apache.org/jira/browse/KAFKA-15146 Project: Kafka

[GitHub] [kafka-site] divijvaidya commented on pull request #531: Add CVE-2023-34455 to cve-list

divijvaidya commented on PR #531: URL: https://github.com/apache/kafka-site/pull/531#issuecomment-1620427926 @ijuma @showuon @jlprat @mimaison please review. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abov

[GitHub] [kafka-site] divijvaidya opened a new pull request, #531: Add CVE-2023-34455 to cve-list

divijvaidya opened a new pull request, #531: URL: https://github.com/apache/kafka-site/pull/531 ## Change Add details about CVE-2023-34455 to cve-list section of the website as an action item from discussion in the mailing list secur...@kafka.apache.org. ## FAQs 1. What vers

[jira] [Resolved] (KAFKA-15140) Improve TopicCommandIntegrationTest to be less flaky

[ https://issues.apache.org/jira/browse/KAFKA-15140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divij Vaidya resolved KAFKA-15140. -- Fix Version/s: 3.6.0 Reviewer: Divij Vaidya Resolution: Fixed > Improve TopicC

Re: [VOTE] KIP-793: Allow sink connectors to be used with topic-mutating SMTs

Hi, +1 (binding) Thanks for the KIP Mickael On Mon, Jul 3, 2023 at 8:18 PM Greg Harris wrote: > > Hey Yash, > > Thanks so much for your effort in the design and discussion phase! > > +1 (non-binding) > > Greg > > On Mon, Jul 3, 2023 at 7:19 AM Chris Egerton wrote: > > > > Hi Yash, > > > > Tha

[jira] [Resolved] (KAFKA-15144) MM2 Checkpoint downstreamOffset stuck to 1

[ https://issues.apache.org/jira/browse/KAFKA-15144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edoardo Comar resolved KAFKA-15144. --- Resolution: Not A Bug Closing as not a bug. The "problem" arose as without config changes,

Re: [DISCUSS] KIP-910: Update Source offsets for Source Connectors without producing records

Hi Sagar, Thanks for your continued work on this KIP! Here are my thoughts on your updated proposal: 1) In the proposed changes section where you talk about modifying the offsets, could you please clarify that tasks shouldn't modify the offsets map that is passed as an argument? Currently, the di

Re: KIP-919: Allow AdminClient to Talk Directly with the KRaft Controller Quorum

Hi Colin, Thanks for the answers to my previous questions. > Yes, the common thread here is that all of these shell commands perform operations can be done without the broker. So it's reasonable to allow them to be done without going through the broker. I don't know if we need a separate note for

Re: KIP-919: Allow AdminClient to Talk Directly with the KRaft Controller Quorum

Hi Colin, Thanks for the KIP. 1. It mentions kafka-configs.sh as one of the affected tools, but doesn't mention that ControllerApis doesn't currently support DESCRIBE_CONFIGS. I think this is worth noting as it is, in effect, a change to the wire protocol accepted by the controller, even if it's

[jira] [Created] (KAFKA-15145) AbstractWorkerSourceTask re-processes records filtered out by SMTs on retriable exceptions

Yash Mayya created KAFKA-15145: -- Summary: AbstractWorkerSourceTask re-processes records filtered out by SMTs on retriable exceptions Key: KAFKA-15145 URL: https://issues.apache.org/jira/browse/KAFKA-15145

Re: [DISCUSS] KIP-942: Add Power(ppc64le) support

Hi, Thanks for the KIP! In the Test Plan section you mentioned a few unit and integration tests are failing. Are these flaky tests or did you find issues related to ppc64le? If they are just flaky tests, I think we can remove that table and instead describe how often we intend to run the tests in