Conditional Produce in Kafka (KAFKA-2260)

Hi all, I am new to the Kafka project and while having a discussion with a colleague, I was pointed to the JIRA KAFKA-2260 [1] which talks about adding the ability to perform "conditional produce" requests to Kafka. This idea sounded very

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

See Changes: -- [...truncated 486467 lines...] [2021-08-24T00:10:35.937Z] > Task :raft:testClasses UP-TO-DATE [2021-08-24T00:10:35.937Z] > Task :connect:json:testJar

[jira] [Created] (KAFKA-13224) broker.id does not appear in config's originals map when setting just node.id

Ron Dagostino created KAFKA-13224: - Summary: broker.id does not appear in config's originals map when setting just node.id Key: KAFKA-13224 URL: https://issues.apache.org/jira/browse/KAFKA-13224

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

See Changes: -- [...truncated 488967 lines...] [Pipeline] { [Pipeline] sh [2021-08-23T22:06:07.621Z] [2021-08-23T22:06:07.621Z] LogCleanerParameterizedIntegrationTest >

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.0 #115

See

Build failed in Jenkins: Kafka » Kafka Branch Builder » 2.8 #68

See Changes: -- [...truncated 3691 lines...] [2021-08-23T21:06:25.662Z] > Task :spotlessScalaCheck [2021-08-23T21:06:32.733Z] [2021-08-23T21:06:32.733Z] > Task :rat

Re: [VOTE] KIP-748: Add Broker Count Metrics (restarted)

Thanks, Colin. Looks good to me! +1 binding -David On Mon, Aug 16, 2021 at 3:37 PM David Jacot wrote: > Hi Colin, > > Thanks for restarting this KIP. > > +1 (binding) > > Best, > David > > Le lun. 16 août 2021 à 21:32, Colin McCabe a écrit : > > > Hi all, > > > > Two months ago we tried to

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

See Changes: -- [...truncated 489110 lines...] [2021-08-23T20:16:18.829Z] > Task :raft:testClasses UP-TO-DATE [2021-08-23T20:16:18.829Z] > Task :connect:json:testJar

Re: [DISCUSS] KIP-768: Extend SASL/OAUTHBEARER with Support for OIDC

Hi Kirk, Thanks for the KIP! 1. Do we want to support validating issuers using the issuer uri? 2. Can the access token be reused for multiple connections from the same client? 3. Do we support configuring separate ssl configs for connecting authorization server/jwks endpoint? 4. Do we want

[jira] [Resolved] (KAFKA-13223) Idempotent producer error with Kraft

[ https://issues.apache.org/jira/browse/KAFKA-13223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurynas Butkus resolved KAFKA-13223. - Resolution: Information Provided > Idempotent producer error with Kraft >

[jira] [Reopened] (KAFKA-13223) Idempotent producer error with Kraft

[ https://issues.apache.org/jira/browse/KAFKA-13223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurynas Butkus reopened KAFKA-13223: - > Idempotent producer error with Kraft > - > >

[jira] [Resolved] (KAFKA-13223) Idempotent producer error with Kraft

[ https://issues.apache.org/jira/browse/KAFKA-13223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurynas Butkus resolved KAFKA-13223. - Fix Version/s: 3.0.0 Resolution: Fixed > Idempotent producer error with Kraft >

Jenkins build became unstable: Kafka » Kafka Branch Builder » 3.0 #114

See

[jira] [Resolved] (KAFKA-13091) Increment HW after shrinking ISR through AlterIsr

[ https://issues.apache.org/jira/browse/KAFKA-13091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-13091. - Fix Version/s: 3.0.1 Resolution: Fixed > Increment HW after shrinking ISR

[jira] [Created] (KAFKA-13223) Idempotent producer error with Kraft

Laurynas Butkus created KAFKA-13223: --- Summary: Idempotent producer error with Kraft Key: KAFKA-13223 URL: https://issues.apache.org/jira/browse/KAFKA-13223 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-770: Replace "buffered.records.per.partition" with "input.buffer.max.bytes"

Thanks Guozhang. 1) Just for my confirmation, when you say we should proceed with the even distribution of bytes, are you referring to the Proposed Solution in the KIP or the option you had considered in the JIRA? 2) Default value for the config is something that I missed. I agree we can't have

Re: [VOTE] KIP-690: Add additional configuration to control MirrorMaker 2 internal topics naming convention

Thanks, everyone for the feedback and votes. I'm closing the vote with: - 3 +1 (binding) votes from Mickael, Gwen and David - 4 +1 (non-binding) votes from Ryanne, Igor, Lopo and Josep On Mon, Aug 23, 2021 at 11:31 AM David Jacot wrote: > +1 (binding). Thanks for the KIP, Omnia. > >

Re: [VOTE] KIP-690: Add additional configuration to control MirrorMaker 2 internal topics naming convention

+1 (binding). Thanks for the KIP, Omnia. On Mon, Aug 23, 2021 at 11:42 AM Omnia Ibrahim wrote: > Can I get one last +1 binding for this KIP, please? > > On Mon, Aug 16, 2021 at 5:16 PM Omnia Ibrahim > wrote: > > > Thanks Gwen. > > Can I get one more +1 binding for the KIP? > > > > On Mon, Aug

Re: [VOTE] KIP-690: Add additional configuration to control MirrorMaker 2 internal topics naming convention

Can I get one last +1 binding for this KIP, please? On Mon, Aug 16, 2021 at 5:16 PM Omnia Ibrahim wrote: > Thanks Gwen. > Can I get one more +1 binding for the KIP? > > On Mon, Aug 2, 2021 at 2:51 AM Gwen Shapira > wrote: > >> +1 (binding). Thank you for your patience and clear explanations,

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

See