Request to contribute to Kafka

my Jira ID: JohnDoe on email zh2725284...@gmail.com Thanks!

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

See

[jira] [Resolved] (KAFKA-14084) Support SCRAM when using KRaft mode

[ https://issues.apache.org/jira/browse/KAFKA-14084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Proven Provenzano resolved KAFKA-14084. --- Resolution: Fixed SCRAM support in KRaft is implemented. Test of SCRAM

[jira] [Created] (KAFKA-14970) Dual write mode testing for SCRAM and Quota

Proven Provenzano created KAFKA-14970: - Summary: Dual write mode testing for SCRAM and Quota Key: KAFKA-14970 URL: https://issues.apache.org/jira/browse/KAFKA-14970 Project: Kafka Issue

Re: Kafka client needs KAFKA-10337 to cover async commit use case

Hey Eric, Maybe its more straightforward to open a new PR. Thanks! P On Fri, May 5, 2023 at 9:36 AM Erik van Oosten wrote: > If I were to rebase the old pull request and re-open KAFKA-10337, would > it be considered for merging? > > Kind regards, > Erik. > > > Op 03-05-2023 om 09:21

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

See

Re: Kafka client needs KAFKA-10337 to cover async commit use case

If I were to rebase the old pull request and re-open KAFKA-10337, would it be considered for merging? Kind regards,     Erik. Op 03-05-2023 om 09:21 schreef Erik van Oosten: Hi Philip, Firstly, could you explain the situation in that you would prefer to invoke commitAsync over commitSync

Re: [DISCUSS] KIP-917: Additional custom metadata for remote log segment

Hi Alexandre, > combining custom > metadata with rlmMetadata increases coupling between Kafka and the > plugin. This is true. However, (if I understand your concern correctly,) rlmMetadata in the current form may be independent from RSM plugins, but data they point to are accessible only via the

[GitHub] [kafka-site] namantam1 closed pull request #501: Update broken link of one of the Kafka Streams use cases.

namantam1 closed pull request #501: Update broken link of one of the Kafka Streams use cases. URL: https://github.com/apache/kafka-site/pull/501 -- 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

[GitHub] [kafka-site] namantam1 commented on pull request #501: Update broken link of one of the Kafka Streams use cases.

namantam1 commented on PR #501: URL: https://github.com/apache/kafka-site/pull/501#issuecomment-1536432784 > Hey @namantam1 Thank you for the change. And welcome to the Kafka community (I see that this is your first change with this repo!). > > We keep the source of truth (for most)

[jira] [Resolved] (KAFKA-14859) Support SCRAM ZK to KRaft Migration

[ https://issues.apache.org/jira/browse/KAFKA-14859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Proven Provenzano resolved KAFKA-14859. --- Resolution: Fixed Merged into trunk and 3.5 > Support SCRAM ZK to KRaft Migration

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

See

Re: [DISCUSS] Apache Kafka 3.5.0 release

Hi David, Thanks for the update! You still own 4 other tickets targeting 3.5: KAFKA-14840, KAFKA-14805, KAFKA-14918, KAFKA-14692. Should I move all of them to the next release? Also KAFKA-14698 and KAFKA-14084 are somewhat related to the migration. Should I move them too? Thanks, Mickael On

Re: [DISCUSS] Apache Kafka 3.5.0 release

Hey Mickael, my two ZK migration fixes are in 3.5 now. Cheers, David On Fri, May 5, 2023 at 9:37 AM Mickael Maison wrote: > Hi Divij, > > Some dependencies (ZooKeeper, Snappy, Swagger, zstd, etc) have been > updated since 3.4. > Regarding your PR, I would have been in favor of bringing this to

Re: [DISCUSS] Apache Kafka 3.5.0 release

Hi Divij, Some dependencies (ZooKeeper, Snappy, Swagger, zstd, etc) have been updated since 3.4. Regarding your PR, I would have been in favor of bringing this to 3.5 a couple of weeks ago, but we're now a week past code freeze for 3.5. Apart if this fixes CVEs, or significant bugs, I think we

[jira] [Created] (KAFKA-14969) Upgrade Mockito to 4.11.0

Divij Vaidya created KAFKA-14969: Summary: Upgrade Mockito to 4.11.0 Key: KAFKA-14969 URL: https://issues.apache.org/jira/browse/KAFKA-14969 Project: Kafka Issue Type: Improvement

Re: Request to contribute to Kafka

Hi, I've granted you permissions on the wiki and Jira. Thanks for your interest in Kafka! Thanks, Mickael On Thu, May 4, 2023 at 3:15 PM Lianet M. wrote: > > Wiki ID: lianetmr > > Jira ID: lianetm > > Both on email liane...@gmail.com > > > Thanks! > > Lianet Magrans

[jira] [Created] (KAFKA-14968) Consumer Notification Callback

Hendrik Jan van Randen created KAFKA-14968: -- Summary: Consumer Notification Callback Key: KAFKA-14968 URL: https://issues.apache.org/jira/browse/KAFKA-14968 Project: Kafka Issue

Re: Question: CI Pipeline in Kafka GitHub Pull Requests & Github Actions Usage

Dear David: I greatly appreciate your welcome and the explanation that you offered regarding the Jenkins system! I will try to familiarize myself with the standards and contribution process of the Kafka community, and look forward to making some contributions in the coming days. Best regards,

[jira] [Resolved] (KAFKA-14926) Remove metrics on Log Cleaner shutdown

[ https://issues.apache.org/jira/browse/KAFKA-14926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-14926. - Resolution: Fixed > Remove metrics on Log Cleaner shutdown >

Re: [DISCUSS] Apache Kafka 3.5.0 release

Hey Mickael Should we consider performing an update of the minor versions of the dependencies in 3.5 (per https://github.com/apache/kafka/pull/13673)? -- Divij Vaidya On Tue, May 2, 2023 at 5:48 PM Mickael Maison wrote: > Hi Luke, > > Yes I think it makes sense to backport both to 3.5. > >

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

See

[GitHub] [kafka-site] showuon merged pull request #365: Update ops.html

showuon merged PR #365: URL: https://github.com/apache/kafka-site/pull/365 -- 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] divijvaidya commented on pull request #501: Update broken link of one of the Kafka Streams use cases.

divijvaidya commented on PR #501: URL: https://github.com/apache/kafka-site/pull/501#issuecomment-1535927663 Hey @namantam1 Thank you for the change. And welcome to the Kafka community (I see that this is your first change with this repo!). We keep the source of truth (for most)

[GitHub] [kafka-site] divijvaidya commented on pull request #365: Update ops.html

divijvaidya commented on PR #365: URL: https://github.com/apache/kafka-site/pull/365#issuecomment-1535919387 Hey @jaapterwoerds Thank you for the contributions and welcome to the Kafka community (I noticed that this is your first contribution!). As you might already be aware,

[jira] [Resolved] (KAFKA-14963) Incorrect partition count metrics for kraft controllers

[ https://issues.apache.org/jira/browse/KAFKA-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-14963. --- Resolution: Fixed > Incorrect partition count metrics for kraft controllers >