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

Hi Mickael, Thank you for looking into this. This is definitely a typo, I've just corrected it. Thanks for finding this! Michael ср, 17 авг. 2022 г. в 15:28, Mickael Maison : > Hi Michael, > > Thanks for the KIP! Sorry for the delay, I finally took some time to > take a look. > > In both the

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

See

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

Hello, I'd like to start a vote on KIP-860, which adds a client-provided option to the AlterPartitionReassignmentsRequest that allows the user to guard against an unintentional change in the replication factor during partition reassignments. Discuss Thread:

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

Thanks David, I do prefer the `disallow-replication-factor-change` flag but only for the CLI. I assume that's what you're proposing instead of "disable-replication-factor-change". The wording is more natural in your suggestion I feel. If we were to modify more (e.g RPC, Admin API), I think it'd

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

See Changes: -- [...truncated 419041 lines...] [2022-08-22T20:45:11.955Z] > Task :connect:api:testJar [2022-08-22T20:45:11.955Z] > Task :connect:api:testSrcJar

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

This looks like a typo yes. We are adding the ability to add a ‘namespace’ which can be prefixed onto the schema name. Regards, Patrick On 2022/08/17 09:28:27 Mickael Maison wrote: > Hi Michael, > > Thanks for the KIP! Sorry for the delay, I finally took some time to > take a look. > > In both

[jira] [Resolved] (KAFKA-13911) Rate is calculated as NaN for minimum config values

[ https://issues.apache.org/jira/browse/KAFKA-13911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jose Armando Garcia Sancio resolved KAFKA-13911. Reviewer: Ismael Juma Resolution: Fixed Closing as it was

[jira] [Resolved] (KAFKA-13410) KRaft Upgrades

[ https://issues.apache.org/jira/browse/KAFKA-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Arthur resolved KAFKA-13410. -- Resolution: Fixed The unfinished tasks from this issue were moved to KAFKA-14175 > KRaft

[jira] [Resolved] (KAFKA-13935) Factor out static IBP usages from broker

[ https://issues.apache.org/jira/browse/KAFKA-13935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Arthur resolved KAFKA-13935. -- Assignee: David Arthur Resolution: Fixed > Factor out static IBP usages from broker >

[jira] [Created] (KAFKA-14175) KRaft Upgrades Part 2

David Arthur created KAFKA-14175: Summary: KRaft Upgrades Part 2 Key: KAFKA-14175 URL: https://issues.apache.org/jira/browse/KAFKA-14175 Project: Kafka Issue Type: Bug Reporter:

[jira] [Created] (KAFKA-14174) Documentation for KRaft

Jose Armando Garcia Sancio created KAFKA-14174: -- Summary: Documentation for KRaft Key: KAFKA-14174 URL: https://issues.apache.org/jira/browse/KAFKA-14174 Project: Kafka Issue

[jira] [Resolved] (KAFKA-13166) EOFException when Controller handles unknown API

[ https://issues.apache.org/jira/browse/KAFKA-13166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-13166. - Resolution: Fixed > EOFException when Controller handles unknown API >

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

See Changes: -- [...truncated 419361 lines...] [2022-08-22T17:01:32.580Z] [2022-08-22T17:01:32.580Z] StreamsAssignmentScaleTest > testStickyTaskAssignorManyStandbys

RE: ARM/PowerPC builds

I am planning to raise a PR for re-enabling PowerPC on the pipeline. I will be monitoring PowerPC for failures. I hope this resolves the concern about build failures on PowerPC. Let me know otherwise. Thanks, Amit Baheti -Original Message- From: Amit Ramswaroop Baheti Sent: 10

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

See

Re: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Hi All, As per the suggestions from David/Guozhang above, I updated the page for Connect to have it's own set of APIs and not extend the ones from consumer. Plz review again. @Luke, Thank you. I am actually looking for review comments/thoughts/suggestions as Connect changes are still in draft

[jira] [Created] (KAFKA-14173) TopologyTestDriver does not perform left join on two streams when right side is missing

Guido Josquin created KAFKA-14173: - Summary: TopologyTestDriver does not perform left join on two streams when right side is missing Key: KAFKA-14173 URL: https://issues.apache.org/jira/browse/KAFKA-14173

[jira] [Resolved] (KAFKA-14097) Separate configuration for producer ID expiry

[ https://issues.apache.org/jira/browse/KAFKA-14097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-14097. - Fix Version/s: 3.4.0 Reviewer: David Jacot Assignee: Justine Olshan

Re: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Hi David, Thanks for the update. Some more questions: 1. In Group Coordinator section, you mentioned: > The new group coordinator will have a state machine per *__consumer_offsets* partitions, where each state machine is modelled as an event loop. Those state machines will be executed in

Re: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Hi Sagar, I have some thoughts about Kafka Connect integrating with KIP-848, but I think we should have a separate discussion thread for the Kafka Connect KIP: Integrating Kafka Connect With New Consumer Rebalance Protocol [1], and let this discussion thread focus on consumer rebalance protocol,