Re: ARM/PowerPC builds

Sorry I just noticed this email now, is this still necessary? I noticed the failures when doing the testing round for the latest Kafka release. -- Matthew de Detrich Aiven Deutschland GmbH Immanuelkirchstraße 26, 10405 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saare

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

Hi Stanislav, Thanks for the KIP. The solution looks reasonable to me. +1 from me. Thank you. Luke On Tue, Aug 23, 2022 at 6:07 AM Stanislav Kozlovski wrote: > Hello, > > I'd like to start a vote on KIP-860, which adds a client-provided option to > the AlterPartitionReassignmentsRequest that a

Re: [VOTE] KIP-855: Add schema.namespace parameter to SetSchemaMetadata SMT in Kafka Connect

Hi, +1 (binding) Thanks for the KIP! On Thu, Jul 28, 2022 at 7:39 AM Michael Negodaev wrote: > > I would like to start a vote on my design to add "schema.namespace" > parameter in SetSchemaMetadata Single Message Transform in Kafka Connect. > > KIP URL: https://cwiki.apache.org/confluence/x/CiT1

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

See Changes: -- [...truncated 338461 lines...] [2022-08-23T12:09:25.614Z] > Task :connect:json:generateMetadataFileForMavenJavaPublication [2022-08-23T12:09:25.614Z] > Tas

[jira] [Resolved] (KAFKA-13971) Atomicity violations caused by improper usage of ConcurrentHashMap

[ https://issues.apache.org/jira/browse/KAFKA-13971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-13971. --- Fix Version/s: 3.4.0 Reviewer: Chris Egerton Resolution: Fixed > Atomicity v

Re: [DISCUSS] KIP-855: Add schema.namespace parameter to SetSchemaMetadata SMT in Kafka Connect

Hi Michael, Thanks for the KIP! I was initially a little skeptical about the usefulness of this feature since it seemed designed exclusively with Avro in mind, but the motivation section convinced me that this would be applicable to a wider range of use cases, so I'm happy to move forward with it.

[jira] [Created] (KAFKA-14176) Reduce visibility of WorkerConfig.lookupKafkaClusterId

Mickael Maison created KAFKA-14176: -- Summary: Reduce visibility of WorkerConfig.lookupKafkaClusterId Key: KAFKA-14176 URL: https://issues.apache.org/jira/browse/KAFKA-14176 Project: Kafka Is

[jira] [Resolved] (KAFKA-14160) Streamline clusterId retrieval in Connect

[ https://issues.apache.org/jira/browse/KAFKA-14160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-14160. Fix Version/s: 3.4.0 Reviewer: Chris Egerton Resolution: Fixed > Streamlin

[jira] [Created] (KAFKA-14177) Correctly support older kraft versions without FeatureLevelRecord

Colin McCabe created KAFKA-14177: Summary: Correctly support older kraft versions without FeatureLevelRecord Key: KAFKA-14177 URL: https://issues.apache.org/jira/browse/KAFKA-14177 Project: Kafka

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #1167

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #1168

See

[GitHub] [kafka-site] bbejeck commented on a diff in pull request #431: Brain Station 23 adopted Kafka

bbejeck commented on code in PR #431: URL: https://github.com/apache/kafka-site/pull/431#discussion_r953115247 ## powered-by.html: ## @@ -2,6 +2,12 @@

[jira] [Created] (KAFKA-14178) NoOpRecord incorrectly causes high controller queue time metric

David Arthur created KAFKA-14178: Summary: NoOpRecord incorrectly causes high controller queue time metric Key: KAFKA-14178 URL: https://issues.apache.org/jira/browse/KAFKA-14178 Project: Kafka

Re: [VOTE] KIP-837 Allow MultiCasting a Result Record.

Thanks for the updates, it reads much more clearly to me now. Looks great +1 (binding) Cheers, Sophie On Fri, Aug 19, 2022 at 1:42 AM Sagar wrote: > Thanks Sophie for the review. I see the confusion. As you pointed out, the > problem the KIP is trying to solve is not the avoidance of a custom

Re: [DISCUSS] KIP-857: Streaming recursion in Kafka Streams

Hey Nick, Sounds like an interesting KIP, and I agree the current way of achieving this in Streams seems wildly overcomplicated. So I'm definitely +1 on adding a smooth API that abstracts away a lot of the complexity and unnecessary topic management. That said, I've found much of the discussion s

[jira] [Resolved] (KAFKA-13981) metadata shell doesn't recognize some new record types

[ https://issues.apache.org/jira/browse/KAFKA-13981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13981. --- Resolution: Duplicate > metadata shell doesn't recognize some new record types > ---

[GitHub] [kafka-site] sadatrafsan commented on pull request #431: Brain Station 23 adopted Kafka

sadatrafsan commented on PR #431: URL: https://github.com/apache/kafka-site/pull/431#issuecomment-1225242243 > Hi @sadatrafsan, thanks for the PR - can you add the image `bs-23.png` to the `images/powered-by` directory? remote: Permission to apache/kafka-site.git denied to sadatrafsan

[GitHub] [kafka-site] sadatrafsan commented on pull request #431: Brain Station 23 adopted Kafka

sadatrafsan commented on PR #431: URL: https://github.com/apache/kafka-site/pull/431#issuecomment-1225247466 image added to the instructed folder -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to t