Re: [VOTE] KIP-1004: Enforce tasks.max property in Kafka Connect

Hi Chris, +1 (binding), thanks for the KIP. Based on discussion in other threads, it looks like the community is aligned with having a 3.8 release before the 4.0 release so we should be able to remove the 'tasks.max.enforce' connector property in 4.0 (we'd discussed potentially having to live

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

See

Re: [DISCUSS] KIP-939: Support Participation in 2PC

Hi Artem, I saw your response in the thread I started discussing Kafka distributed transaction support and the XA interface. I would like to work with you to add XA support to Kafka on top of the excellent foundational work that you have started with KIP-939. I agree that explicit XA support

Re: [DISCUSS] KIP-995: Allow users to specify initial offsets while creating connectors

Thanks Chris, It makes sense to call out the cleaning up of existing offsets in the KIP. I have made the change and will initiate the voting in a day. Regards, Ashwin On Tue, Dec 12, 2023 at 6:57 PM Chris Egerton wrote: > Hi Ashwin, > > LGTM! One small adjustment I'd suggest but we don't have

Re: [VOTE] KIP-1013: Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7)

Hi Mickael, Good catch. I fixed that and one other (similar) case (they were remnants of an earlier version of the proposal). Ismael On Wed, Jan 3, 2024 at 8:59 AM Mickael Maison wrote: > Hi Ismael, > > I'm +1 (binding) too. > > One small typo, the KIP states "The remaining modules (clients,

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

See

Re: [DISCUSS] Kafka distributed transaction support

Hi Rowland, KIP-939 provides a foundation for using a two-phase commit protocol with Kafka (allows it to be a participant) that can be used to implement various concrete protocols, such as XA but not only XA. The benefit of supporting a foundational construct (and not just one concrete protocol

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.7 #46

See

[jira] [Created] (KAFKA-16078) InterBrokerProtocolVersion defaults to non-production MetadataVersion

David Arthur created KAFKA-16078: Summary: InterBrokerProtocolVersion defaults to non-production MetadataVersion Key: KAFKA-16078 URL: https://issues.apache.org/jira/browse/KAFKA-16078 Project: Kafka

Re: [DISCUSS] Connect Jira component name

Hey Connect Developers, I have changed the Jira component name from "KafkaConnect" to "connect". Thanks Ismael and Matthias for your support! Greg On Tue, Jan 2, 2024 at 2:34 AM Matthias J. Sax wrote: > > SGTM. > > I found it always odd that it's named `KafkaConnect` :) > > > -Matthias > > On

Re: [VOTE] KIP-1004: Enforce tasks.max property in Kafka Connect

Hey Chris, Thanks for the KIP! I think the aggressive default and deprecation schedule is the right choice for this change. +1 (binding) On Wed, Jan 3, 2024 at 9:01 AM Mickael Maison wrote: > > Hi Chris, > > +1 (binding), thanks for the KIP > > Mickael > > On Tue, Jan 2, 2024 at 8:55 PM Hector

[jira] [Created] (KAFKA-16077) State updater fails to close task when input partitions are updated

Lucas Brutschy created KAFKA-16077: -- Summary: State updater fails to close task when input partitions are updated Key: KAFKA-16077 URL: https://issues.apache.org/jira/browse/KAFKA-16077 Project:

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

See

Re: [DISCUSS] KIP-971 Expose replication-offset-lag MirrorMaker2 metric

Hi all, Here is the vote thread: https://lists.apache.org/thread/ftlnolcrh858dry89sjg06mdcdj9mrqv Cheers! On Wed, 27 Dec 2023 at 11:23, Elxan Eminov wrote: > Hi all, > I've updated the KIP with the details we discussed in this thread. > I'll call in a vote after the holidays if everything

[VOTE] KIP-971: Expose replication-offset-lag MirrorMaker2 metric

Hi All, I'd like to initiate a vote for KIP-971. This KIP is about adding a new metric to the MirrorSourceTask that tracks the offset lag between a source and a target partition. KIP link:

Re: [VOTE] KIP-1013: Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7)

Hi Ismael, I'm happy to see the minimum Java version moving forward, even if it's just for the broker and tools. I hope that this encourages operators to upgrade to 17+ across-the-board, and will make it easier to drop support for 11 in the other modules in 5.0. +1 (binding) Thanks, Greg On

Re: [VOTE] KIP-1004: Enforce tasks.max property in Kafka Connect

Hi Chris, +1 (binding), thanks for the KIP Mickael On Tue, Jan 2, 2024 at 8:55 PM Hector Geraldino (BLOOMBERG/ 919 3RD A) wrote: > > +1 (non-binding) > > Thanks Chris! > > From: dev@kafka.apache.org At: 01/02/24 11:49:18 UTC-5:00To: > dev@kafka.apache.org > Subject: Re: [VOTE] KIP-1004:

Re: [VOTE] KIP-1013: Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7)

Hi Ismael, I'm +1 (binding) too. One small typo, the KIP states "The remaining modules (clients, streams, connect, tools, etc.) will continue to support Java 11.". I think we want to remove support for Java 11 in the tools module so it shouldn't be listed here. Thanks, Mickael On Wed, Jan 3,

Re: Adding reviewers with Github actions

Hey all, So finally I had some time for some lower prio stuff since everyone is still on holiday. I've implemented this Github action check in a PR: https://github.com/apache/kafka/pull/15115 It uses the Github API to fetch the name and email of the user based on the username who submitted the

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

See

Re: [VOTE] KIP-1013: Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7)

+1 (binding) -- Divij Vaidya On Wed, Jan 3, 2024 at 11:06 AM Viktor Somogyi-Vass wrote: > Hi Ismael, > > I think it's important to make this change, the youtube video you posted on > the discussion thread makes very good arguments and so does the KIP. Java 8 > is almost a liability and Java

Re: [VOTE] KIP-1013: Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7)

Hi Ismael, I think it's important to make this change, the youtube video you posted on the discussion thread makes very good arguments and so does the KIP. Java 8 is almost a liability and Java 11 already has smaller (and decreasing) adoption than 17. It's a +1 (binding) from me. Thanks, Viktor

[jira] [Resolved] (KAFKA-16046) Stream Stream Joins fail after restoration with deserialization exceptions

[ https://issues.apache.org/jira/browse/KAFKA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski resolved KAFKA-16046. - Resolution: Fixed > Stream Stream Joins fail after restoration with

Re: Apache Kafka 3.7.0 Release

Hey all, happy new year. Thanks for the heads up Almog. Makes sense. To give an update - I haven't been able to resolve the gradlewAll publish failure, and as such haven't been able to release an RC. As a minor barrier, I have to also update the year in the NOTICE file, otherwise the release