Re: [ANNOUNCE] New Kafka PMC member: David Jacot

Congrats! On Fri, Dec 17, 2021, at 8:55 PM, Luke Chen wrote: > Congrats, David! > Well deserved. > > Luke > > deng ziming 於 2021年12月18日 週六 上午7:47 寫道： > > > Congrats David! > > > > -- > > Ziming Deng > > > > > On Dec 18, 2021, at 7:08 AM, Gwen Shapira wrote: > > > > > > Hi everyone, > > > > >

Re: [ANNOUNCE] New Kafka PMC member: David Jacot

Congrats, David! Well deserved. Luke deng ziming 於 2021年12月18日 週六 上午7:47 寫道： > Congrats David! > > -- > Ziming Deng > > > On Dec 18, 2021, at 7:08 AM, Gwen Shapira wrote: > > > > Hi everyone, > > > > David Jacot has been an Apache Kafka committer since Oct 2020 and has > been contributing to

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

See

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.1 #35

See Changes: -- [...truncated 501833 lines...] [2021-12-18T01:42:24.803Z] TopicCommandIntegrationTest > testCreateWithInvalidReplicationFactor() STARTED

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

See

[jira] [Resolved] (KAFKA-13544) Deadlock during shutting down kafka broker because of connectivity problem with zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-13544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13544. - Fix Version/s: 3.2.0 Resolution: Fixed Merged the PR to trunk. > Deadlock during shutting down

[jira] [Created] (KAFKA-13555) Consider number if input topic partitions for task assignment

Matthias J. Sax created KAFKA-13555: --- Summary: Consider number if input topic partitions for task assignment Key: KAFKA-13555 URL: https://issues.apache.org/jira/browse/KAFKA-13555 Project: Kafka

Re: [ANNOUNCE] New Kafka PMC member: David Jacot

Congrats David! -- Ziming Deng > On Dec 18, 2021, at 7:08 AM, Gwen Shapira wrote: > > Hi everyone, > > David Jacot has been an Apache Kafka committer since Oct 2020 and has been > contributing to the community consistently this entire time - especially > notable the fact that he reviewed

Re: [ANNOUNCE] New Kafka PMC member: David Jacot

Congratulations David! Well deserved. -Bill On Fri, Dec 17, 2021 at 6:43 PM José Armando García Sancio wrote: > Congrats David! > > On Fri, Dec 17, 2021 at 3:09 PM Gwen Shapira wrote: > > > > Hi everyone, > > > > David Jacot has been an Apache Kafka committer since Oct 2020 and has > been

Re: [ANNOUNCE] New Kafka PMC member: David Jacot

Congrats David! On Fri, Dec 17, 2021 at 3:09 PM Gwen Shapira wrote: > > Hi everyone, > > David Jacot has been an Apache Kafka committer since Oct 2020 and has been > contributing to the community consistently this entire time - especially > notable the fact that he reviewed around 150 PRs in

Re: [DISCUSS] Apache Kafka 3.1.0 release

Hi David Jacot, I cherry picked this commit https://github.com/apache/kafka/pull/11511 to the 3.1 branch to fix the kafka.metrics.MetricsTest integration tests for that branch. Thanks, -Jose On Tue, Dec 14, 2021 at 8:09 AM David Jacot wrote: > > Hi Jason, > > Thanks for bringing this up. I do

[jira] [Created] (KAFKA-13554) Rename RangeQuery to KeyRangeQuery

John Roesler created KAFKA-13554: Summary: Rename RangeQuery to KeyRangeQuery Key: KAFKA-13554 URL: https://issues.apache.org/jira/browse/KAFKA-13554 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-13553) Add DSL stores to IQv2StoreIntegrationTest

John Roesler created KAFKA-13553: Summary: Add DSL stores to IQv2StoreIntegrationTest Key: KAFKA-13553 URL: https://issues.apache.org/jira/browse/KAFKA-13553 Project: Kafka Issue Type:

[ANNOUNCE] New Kafka PMC member: David Jacot

Hi everyone, David Jacot has been an Apache Kafka committer since Oct 2020 and has been contributing to the community consistently this entire time - especially notable the fact that he reviewed around 150 PRs in the last year. It is my pleasure to announce that David agreed to join the Kafka

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

See

Re: [VOTE] KIP-778 KRaft upgrades

The vote has passed with the following results: 4 binding votes from: Guozhang, José, Colin, and Jun 2 non-binding votes from: Ziming Deng and Kowshik no -1 votes Thanks to everyone for all the thoughtful feedback for this KIP. Much appreciated! -David On Fri, Dec 17, 2021 at 12:36 PM Jun Rao

Re: [VOTE] KIP-778 KRaft upgrades

Thanks, David. +1 from me. Jun On Fri, Dec 17, 2021 at 7:59 AM David Arthur wrote: > Yes we'll need to bump ApiVersions request/response version to 4. I have a > small note in the Public Interfaces that we'll drop MinVersionLevel in > ApiVersionsResponse version 4. > > I believe we can avoid

Re: [DISCUSS] KIP-778 KRaft Upgrades

Tom, thanks for taking a look! 1. Yes you're right, I'll fix that 2. Components refers to broker objects like ReplicaManager, ClientQuotaManager, etc. Controller components (so far) don't need to reload any state based on metadata.version changes. 3. Yes, if a controller reads a

Re: [DISCUSS] KIP-778 KRaft Upgrades

Hi David, Thanks for the KIP. Sorry I'm so late in looking at this. I have a few questions. 1. In the Proposed Changes Overview it says "The controller validates that the cluster can be safely downgraded to this version (override with --force)" I think that be "--unsafe"? 2. Also in this

Re: [VOTE] KIP-778 KRaft upgrades

Yes we'll need to bump ApiVersions request/response version to 4. I have a small note in the Public Interfaces that we'll drop MinVersionLevel in ApiVersionsResponse version 4. I believe we can avoid bumping the version of FeatureLevelRecord since KRaft doesn't support the UpgradeFeatures RPC

Re: [VOTE] KIP-806: Add session and window query over KV-store in IQv2

Thanks everyone for voting. Voting passed with the following +1s: - Luke Chen - Guozhang Wang (binding) - John Roesler (binding) - Bruno Cadonna (binding) I'll update the KIP status accordingly. Best, Patrick On Thu, Dec 16, 2021 at 2:09 PM Bruno Cadonna wrote: > Hi Partick, > > Thank you

Understanding the SASL/PLAIN mechanism

Hello Kafka Dev, I realize that this question might be more SASL than Kafka related, but after endless Googling and code browsing, I'm not understanding a few things. I've looked at all of the code for SASL/PLAIN and SASL/OAUTHBEARER but when attempting to implement my own custom SASL

Re: [DISCUSS] Please review the 3.1.0 blog post

Hi Tom, Thanks for your inputs. I have updated the blog post. Best, David On Thu, Dec 16, 2021 at 3:07 PM Tom Bentley wrote: > > Hi David, > > A couple of minor nits: > > For KIP-783: "This field is set for any exception that originates from, or > tied to, a specific task." should be "This