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

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/CiT1D

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

See Changes: -- [...truncated 486773 lines...] [2022-07-28T02:55:11.279Z] > Task :connect:api:testJar [2022-07-28T02:55:11.279Z] > Task :connect:api:testSrcJar

[RESULTS] [VOTE] Release Kafka version 3.2.1

The vote for RC3 has passed with eight +1 votes (three binding) and no -1 votes. Here are the results: +1 votes PMC: * Randall Hauch * Rajini Sivaram * Bill Bejeck Committers: None Community: * Christopher Shannon * Federico Valeri * Dongjoon Hyun * Jakub Scholz * Matthew de Detrich 0 Votes:

Re: [VOTE] 3.2.1 RC3

I'm closing out the vote now. Thanks to everyone who voted. The RC passed with the required number of votes. I'll send out the results thread shortly. Cheers, David Arthur On Wed, Jul 27, 2022 at 11:54 AM Bill Bejeck wrote: > Hi David, > > Thanks for running the release! > > I did the

[jira] [Resolved] (KAFKA-14119) Sensor in metrics has potential thread safety issues

[ https://issues.apache.org/jira/browse/KAFKA-14119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Wu resolved KAFKA-14119. - Resolution: Not A Bug > Sensor in metrics has potential thread safety issues >

Re: [DISCUSS] KIP-859: Add Metadata Log Processing Error Related Metrics

Thanks for the review David. Here are the answers to your questions. I will update the KIP to make the info clearer. > 1) Does "publisher-error-count" represent the number of errors > encountered only when loading the most recent image? Or will this value be > the cumulative number of publisher

[jira] [Created] (KAFKA-14119) Sensor in metrics has potential thread safety issues

Eric Wu created KAFKA-14119: --- Summary: Sensor in metrics has potential thread safety issues Key: KAFKA-14119 URL: https://issues.apache.org/jira/browse/KAFKA-14119 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-859: Add Metadata Log Processing Error Related Metrics

Thanks for the KIP, Niket! I definitely agree we need to surface metadata processing errors to the operator. I have some questions about the semantics of the new metrics: 1) Does "publisher-error-count" represent the number of errors encountered only when loading the most recent image? Or will

[DISCUSS] KIP-859: Add Metadata Log Processing Error Related Metrics

Hi all, I would like to start a discussion on adding some new metrics to KRaft to allow for better visibility into log processing errors. KIP URL: https://cwiki.apache.org/confluence/display/KAFKA/KIP-859%3A+Add+Metadata+Log+Processing+Error+Related+Metrics Thanks! Niket

[jira] [Created] (KAFKA-14118) Generate and persist storage uuiid

José Armando García Sancio created KAFKA-14118: -- Summary: Generate and persist storage uuiid Key: KAFKA-14118 URL: https://issues.apache.org/jira/browse/KAFKA-14118 Project: Kafka

[jira] [Created] (KAFKA-14117) Flaky Test DynamicBrokerReconfigurationTest.testKeyStoreAlter

Hao Li created KAFKA-14117: -- Summary: Flaky Test DynamicBrokerReconfigurationTest.testKeyStoreAlter Key: KAFKA-14117 URL: https://issues.apache.org/jira/browse/KAFKA-14117 Project: Kafka Issue

[jira] [Created] (KAFKA-14116) Update and add all of the Kafka Message Schemas

José Armando García Sancio created KAFKA-14116: -- Summary: Update and add all of the Kafka Message Schemas Key: KAFKA-14116 URL: https://issues.apache.org/jira/browse/KAFKA-14116 Project:

[jira] [Reopened] (KAFKA-12566) Flaky Test MirrorConnectorsIntegrationSSLTest#testReplication

[ https://issues.apache.org/jira/browse/KAFKA-12566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Li reopened KAFKA-12566: Somehow this is still happening: ``` [2022-07-27T11:32:04.461Z] MirrorConnectorsIntegrationSSLTest >

[jira] [Created] (KAFKA-14115) Password configs are logged in plaintext in KRaft

David Arthur created KAFKA-14115: Summary: Password configs are logged in plaintext in KRaft Key: KAFKA-14115 URL: https://issues.apache.org/jira/browse/KAFKA-14115 Project: Kafka Issue

Re: [DISCUSS] KIP-854 Separate configuration for producer ID expiry

I don't think a major release is a requirement for a default change for what it's worth. I do appreciate that there is a preference for not rocking the boat though. For a little bit of background here, the problem we have encountered in production since the idempotent producer became the default

[jira] [Created] (KAFKA-14114) KIP-859: Add Metadata Log Processing Error Related Metrics

Niket Goel created KAFKA-14114: -- Summary: KIP-859: Add Metadata Log Processing Error Related Metrics Key: KAFKA-14114 URL: https://issues.apache.org/jira/browse/KAFKA-14114 Project: Kafka Issue

[jira] [Created] (KAFKA-14113) KIP-856: KRaft Disk Failure Recovery

José Armando García Sancio created KAFKA-14113: -- Summary: KIP-856: KRaft Disk Failure Recovery Key: KAFKA-14113 URL: https://issues.apache.org/jira/browse/KAFKA-14113 Project: Kafka

Re: [VOTE] 3.2.1 RC3

Hi David, Thanks for running the release! I did the following steps: - Validated all signatures and checksums - Built from source - Ran all the unit tests - I spot-checked the doc. I did notice the same version number as Randal - but I expect that will get fixed when the docs

Re: [DISCUSS] KIP-858: Handle JBOD broker disk failure in KRaft

Hi Igor, Thanks for the KIP. Looking forward to this improvement. I'll review your KIP. I should mention that I started a discussion thread on KIP-856: KRaft Disk Failure Recovery at https://lists.apache.org/thread/ytv0t18cplwwwqcp77h6vry7on378jzj Both keep introducing similar concepts. For

[DISCUSS] KIP-856: KRaft Disk Failure Recovery

Hi all, I would like to start the discussion on my design to allow KRaft to detect and recover from disk failures in the minority of voters. For those following the discussion on KIP-853, this is a subset of that KIP with only the mechanisms required to solve the problem described in the

Re: [DISCUSS] KIP-853: KRaft Voters Change

Hi all, Community members Jason Gustafson, Colin P. McCabe and I have been having some offline conversations. At a high-level KIP-853 solves the problems: 1) How can KRaft detect and recover from disk failures on the minority of the voters? 2) How can KRaft support a changing set of voter nodes?

Re: [DISCUSS] Website changes required for Apache projects

Hi all To conclude this thread, all required changes listed for adhering to ASF guidelines (documented at https://issues.apache.org/jira/browse/KAFKA-13868) have been merged to the website. If you find any other aspects where we are not adhering to ASF privacy policy

[GitHub] [kafka-site] mimaison merged pull request #429: KAFKA-13868: Replace embedded YouTube links with hyperlinks on streams page

mimaison merged PR #429: URL: https://github.com/apache/kafka-site/pull/429 -- 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 the specific comment. To unsubscribe, e-mail:

[GitHub] [kafka-site] showuon commented on pull request #429: KAFKA-13868: Replace embedded YouTube links with hyperlinks on streams page

showuon commented on PR #429: URL: https://github.com/apache/kafka-site/pull/429#issuecomment-1196778133 @mimaison , do you want to have another look? -- 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

[GitHub] [kafka-site] divijvaidya commented on pull request #429: KAFKA-13868: Replace embedded YouTube links with hyperlinks on streams page

divijvaidya commented on PR #429: URL: https://github.com/apache/kafka-site/pull/429#issuecomment-1196687885 @mimaison please review. Last one before we can close KAFKA-13868. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [kafka-site] divijvaidya opened a new pull request, #429: KAFKA-13868: Replace embedded YouTube links with hyperlinks on streams page

divijvaidya opened a new pull request, #429: URL: https://github.com/apache/kafka-site/pull/429 This is a hot fix to merge the https://github.com/apache/kafka/pull/12438 into kafka-site to satisfy the ASF privacy policy requirements. ## Testing Tested locally. ![Screenshot

[jira] [Resolved] (KAFKA-13730) OAuth access token validation fails if it does not contain the "sub" claim

[ https://issues.apache.org/jira/browse/KAFKA-13730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-13730. --- Fix Version/s: 3.4.0 Resolution: Fixed > OAuth access token validation fails if it does not

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

Thanks Walker for the comments I have updated the KIP with all the suggestions. Thanks! On Tue, Jul 12, 2022 at 10:59 PM Walker Carlson wrote: > Hi Sagar, > > I just finished reading the KIP and this seems to be a great addition. > > I agree with Matthias that the interface with a default

[DISCUSS] KIP-858: Handle JBOD broker disk failure in KRaft

Hi all, I have proposal to handle JBOD disk failures in KRaft mode. With KIP-833 KRaft is being marked production ready and ZK mode is being deprecated but support for JBOD is still a big feature that's missing. Please have a look and share your thoughts:

Re: [DISCUSS] KIP-854 Separate configuration for producer ID expiry

Thanks Justine for the KIP. I think it might be better to document the correlation between the new config and delivery.timeout.ms in the Public Interfaces Description. Also, I agree with Luke that for now setting a default to -1 should be good. We can look to switch to 1 day with major release.

Re: [DISCUSS] KIP-844: Transactional State Stores

Hey Nick, Thank you for the kind words and the feedback! I'll definitely add an option to configure the transactional mechanism in Stores factory method via an argument as John previously suggested and might add the in-memory option via RocksDB Indexed Batches if I figure why their creation via

Re: [DISCUSS] KIP-844: Transactional State Stores

Hey Guozhang, 1) About the param passed into the `recover()` function: it seems to me > that the semantics of "recover(offset)" is: recover this state to a > transaction boundary which is at least the passed-in offset. And the only > possibility that the returned offset is different than the

Re: [DISCUSS] KIP-853: KRaft Voters Change

Hi Jose, It's looking good! > I think that when a replica has caught up is an implementation detail > and we can have this detailed discussion in Jira or the PR. What do > you think? Yes, that sounds fine. For what it's worth, making the leader take the decision of when an observer is caught-up

Re: [DISCUSS]: Including TLA+ in the repo

+1 for me too. Once the KIP-853 is agreed I will make any necessary changes and submit a PR to the apache/kafka repo. Jack On Tue, Jul 26, 2022 at 10:10 PM Ismael Juma wrote: > I'm +1 for inclusion in the main repo and I was going to suggest the same > in the KIP-853 discussion. The original

[jira] [Created] (KAFKA-14112) Expose replication-offset-lag Mirror metric

Elkhan Eminov created KAFKA-14112: - Summary: Expose replication-offset-lag Mirror metric Key: KAFKA-14112 URL: https://issues.apache.org/jira/browse/KAFKA-14112 Project: Kafka Issue Type: