Re: [DISCUSS] KIP-1052: Enable warmup in producer performance test

Hi Matt, thanks for the updates. Snippets are really useful. > No public interfaces are affected. You mean, no existing public interfaces right? Anyway, this content should be in the "Compatibility, Deprecation, and Migration Plan" section. > The first option, --warmup-records, will be added to

Re: [DISCUSS] KIP-1059: Enable the Producer flush() method to clear the latest send() error

Hi Matthias, Thanks for the valid points you mentioned. I updated the KIP and the PR with: 1) mentioning that the new overloaded `send` throws `IllegalStateException` if the user tries to ignore `send()` errors outside of a transaction. 2) the default implementation in `Producer` interface throws a

[ANNOUNCE] Apache Kafka 3.7.1

The Apache Kafka community is pleased to announce the release for Apache Kafka 3.7.1 This is a bug fix release and it includes fixes and improvements. All of the changes in this release can be found in the release notes: https://www.apache.org/dist/kafka/3.7.1/RELEASE_NOTES.html You can downlo

Re: [DISCUSS] KIP-1056: Remove `default.` prefix for exception handler StreamsConfig

Hi Sophie, Thank you for your analysis! I understand your valid concerns. However, what I do not like about the concern is that it blocks us from ever changing low priority stuff in the code base. Which IMO is bad from a maintainability perspective. I agree that the change makes primarily us

Re: [ANNOUNCE] Apache Kafka 3.7.1

Congratulations! Thanks Igor for running the release. Mickael On Mon, Jul 1, 2024 at 11:26 AM Igor Soarez wrote: > > The Apache Kafka community is pleased to announce the release for Apache > Kafka 3.7.1 > > This is a bug fix release and it includes fixes and improvements. > > All of the chang

[jira] [Created] (KAFKA-17058) Extend CoordinatorRuntime to support non-atomic writes

David Jacot created KAFKA-17058: --- Summary: Extend CoordinatorRuntime to support non-atomic writes Key: KAFKA-17058 URL: https://issues.apache.org/jira/browse/KAFKA-17058 Project: Kafka Issue Ty

Re: [ANNOUNCE] Apache Kafka 3.7.1

Thanks Igor for running this release! Luke On Mon, Jul 1, 2024 at 5:45 PM Mickael Maison wrote: > Congratulations! > > Thanks Igor for running the release. > > Mickael > > On Mon, Jul 1, 2024 at 11:26 AM Igor Soarez wrote: > > > > The Apache Kafka community is pleased to announce the release f

Re: [ANNOUNCE] Apache Kafka 3.7.1

Thanks Igor and all Kafak contributors! Luke Chen 於 2024年7月1日 週一 下午7:10寫道： > Thanks Igor for running this release! > > Luke > > On Mon, Jul 1, 2024 at 5:45 PM Mickael Maison > wrote: > > > Congratulations! > > > > Thanks Igor for running the release. > > > > Mickael > > > > On Mon, Jul 1, 2024

[jira] [Resolved] (KAFKA-17046) Upgrade netty version to 4.1.111.Final

[ https://issues.apache.org/jira/browse/KAFKA-17046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17046. Fix Version/s: 3.9.0 Resolution: Fixed > Upgrade netty version to 4.1.111.Final > -

[jira] [Resolved] (KAFKA-16909) Refactor GroupCoordinatorConfig with AbstractConfig

[ https://issues.apache.org/jira/browse/KAFKA-16909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-16909. Fix Version/s: 3.9.0 Resolution: Fixed > Refactor GroupCoordinatorConfig with Abstr

[jira] [Created] (KAFKA-17059) Remove `dynamicConfigOverride` from KafkaConfig

Chia-Ping Tsai created KAFKA-17059: -- Summary: Remove `dynamicConfigOverride` from KafkaConfig Key: KAFKA-17059 URL: https://issues.apache.org/jira/browse/KAFKA-17059 Project: Kafka Issue Typ

Re: [ANNOUNCE] Apache Kafka 3.7.1

A correction to a funny mistake in my previous message: That's *61 contributors* to this release, not 1086! -- Igor Soarez On Mon, Jul 1, 2024, at 11:25 AM, Igor Soarez wrote: > The Apache Kafka community is pleased to announce the release for Apache > Kafka 3.7.1 > > This is a bug fix release

Re: [ANNOUNCE] Apache Kafka 3.7.1

Hi Igor, Thanks for the release. Since this is the highest version available, we should also promote newer docker image with apache/kafka:latest docker tag. Thanks. On Mon, Jul 1, 2024 at 9:54 PM Igor Soarez wrote: > > A correction to a funny mistake in my previous message: > That's *61 contrib

[jira] [Resolved] (KAFKA-13295) Long restoration times for new tasks can lead to transaction timeouts

[ https://issues.apache.org/jira/browse/KAFKA-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-13295. --- Fix Version/s: 3.8.0 Resolution: Fixed > Long restoration times for new tasks can lea

Re: [VOTE] KIP-1022 Formatting and Updating Features

Hi, David, Yes, that's another option. It probably has its own challenges. For example, the FeatureCommand tool currently treats disabling a feature as setting the version to 0. It would be useful to get Jose's opinion on this since he introduced version 0 in the kraft.version feature. Thanks, J

[jira] [Created] (KAFKA-17060) Rename LegacyKafkaConsumer to ClassicKafkaConsumer

Kirk True created KAFKA-17060: - Summary: Rename LegacyKafkaConsumer to ClassicKafkaConsumer Key: KAFKA-17060 URL: https://issues.apache.org/jira/browse/KAFKA-17060 Project: Kafka Issue Type: Impr

Re: [DISCUSS] KIP-891: Running multiple versions of Connector plugins

Hey Snehashis, Sorry for the late reply, and thanks for helping close out the discussion. > Note that if my assumptions are correct then > this can happen with the existing framework as well, or is there some > safeguard from this happening? Currently, if a cluster has a heterogeneous plugin ins

[DISCUSS] - KIP-1064: Upgrade slf4j to 2.x

Hello, Regarding KIP-1064 [0], I would like to start a discussion on upgrading slf4j to 2.x, which is currently at 1.7.36, and with an option to provide slf4j provider in run class. This is also discussed in jira [1] and git pr [2], and thought we should have a kip. Please note this kip is inten

Re: [ANNOUNCE] Apache Kafka 3.7.1

Hi Manikumar, Thanks for pointing this out. The apache/kafka:latest has now been updated from apache/kafka:3.7.1. Best, -- Igor

Re: [DISCUSS] KIP-1006: Remove SecurityManager Support

Hi Mickael, Thanks for the pointer to that JDK ticket, I did not realize that the legacy APIs were going to be degraded instead of removed. I have updated the KIP to accommodate for this change in the JDK implementation. In addition to detecting the removal of the method/classes, it will also fal

Re: [DISCUSS] KIP-1056: Remove `default.` prefix for exception handler StreamsConfig

Thanks Bruno -- I think shipping this with 4.0 when most users will expect to need code changes anyway is a good compromise. I'm happy to change my position and cast a +1 vote on this. I suppose we will just need to wait a few weeks to actually merge these changes, given the interim short-cycle 3.9

Re: [VOTE] KIP-1056 - Deprecate `default.` prefix for exception handler in StreamsConfig

After reaching an agreement on the discussion thread, I'm giving this a +1 (binding) under the condition that we ship this change in 4.0 so as to minimize the impact on users. Thanks for the KIP! -Sophie On Thu, Jun 27, 2024 at 2:43 PM Sophie Blee-Goldman wrote: > I'll just note that I will pe

Re: [DISCUSS] KIP-1065: Add "retry" return-option to ProductionExceptionHandler

Thanks for the KIP -- definitely agree with this proposal, just have a few suggestions: 1. In the KIP, you mention We might also consider to not calling the handler when writing into > internal topics, as those must exist. Personally I would vote to consider all topics the same in this regard,

Re: [VOTE] KIP-1022 Formatting and Updating Features

Hi David, In the ApiVersionsResponse, we really don't have an easy way of mapping finalizedVersion = 1 to "off" in older releases such as 3.7.0. For example, if a 3.9.0 broker advertises that it has finalized group.version = 1, that will be treated by 3.7.0 as a brand new feature, not as "KIP-8

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

See

Re: [DISCUSS] KIP-1056: Remove `default.` prefix for exception handler StreamsConfig

Hi Sophie, I totally agree on evaluating the impact case by case! Nobody brushed any concerns under any rug. It was merely a concern about a valid concern. I am sorry if it came across as brushing. Great that we found a viable solution! Best, Bruno On 7/2/24 1:01 AM, Sophie Blee-Goldman w

Re: [VOTE] KIP-1056 - Deprecate `default.` prefix for exception handler in StreamsConfig

Thanks for the KIP! +1 (binding) under the conditions Sophie pointed out. Best, Bruno On 7/2/24 1:05 AM, Sophie Blee-Goldman wrote: After reaching an agreement on the discussion thread, I'm giving this a +1 (binding) under the condition that we ship this change in 4.0 so as to minimize the imp