Re: Filtering support on Fetch API

server-side message filter had been talked for a very very long time, I notice serveral years ago kafka community already discuss this feature. kafka community still no plan implement it for some reason: - they dont want to break the fetch zero-copy advantage - kafka think stream project is

[GitHub] [kafka-site] rite2nikhil commented on a change in pull request #392: adding new vulnerability info - CVE-2022-23307

rite2nikhil commented on a change in pull request #392: URL: https://github.com/apache/kafka-site/pull/392#discussion_r789377878 ## File path: cve-list.html ## @@ -9,6 +9,31 @@ Apache Kafka Security Vulnerabilities This page lists all security vulnerabilities fixed in

Re: [DISCUSS] KIP-704: Send a hint to broker if it is an unclean leader

Hi José, Thanks for the changes. "isLeaderRecovering" sounds pretty awkward. If we want to call this "leader recovery" then maybe the flag could be something like "inLeaderRecovery." Actually, how about "inElectionRecovery" to emphasize the fact that we are recovering from an unclean leader

Re: [DISCUSS] KIP-704: Send a hint to broker if it is an unclean leader

Jose, Is there a specific need for adding "isUnclean '' flag to `AlterIsrResponse`. A potential sequence of events will be: 1. Controller sets the flag at `ZK` and informs the leader via the `LeaderAndIsrRequest` 2. Leader undertakes the necessary recovery and sends out a `AlterIsrRequest` to

[GitHub] [kafka-site] junrao commented on a change in pull request #392: adding new vulnerability info - CVE-2022-23307

junrao commented on a change in pull request #392: URL: https://github.com/apache/kafka-site/pull/392#discussion_r789168637 ## File path: cve-list.html ## @@ -9,6 +9,31 @@ Apache Kafka Security Vulnerabilities This page lists all security vulnerabilities fixed in released

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.0 #166

See Changes: -- [...truncated 418006 lines...] [2022-01-20T21:30:52.475Z] [INFO]

Re: [VOTE] KIP-591: Add Kafka Streams config to set default state store

+1 non binding On Thu, Jan 20, 2022 at 2:00 PM Matthias J. Sax wrote: > +1 (binding) > > On 1/20/22 10:52 AM, Guozhang Wang wrote: > > Thanks Luke! I'm +1 on the KIP. > > > > > > Guozhang > > > > On Wed, Jan 19, 2022 at 5:58 PM Luke Chen wrote: > > > >> Hi devs, > >> > >> I'd like to start a

Re: [DISCUSS] KIP-813 Shared State Stores

Any processor that would use that materialized, read-only statestore would need to wait for the store to be restored. I can't find a way to make that possible since processors can't wait for the statestore to be restored. This is built into the runtime already. Nothing to worry about. It's

Re: [VOTE] KIP-591: Add Kafka Streams config to set default state store

+1 (binding) On 1/20/22 10:52 AM, Guozhang Wang wrote: Thanks Luke! I'm +1 on the KIP. Guozhang On Wed, Jan 19, 2022 at 5:58 PM Luke Chen wrote: Hi devs, I'd like to start a vote for the KIP-591: Add Kafka Streams config to set default state store. The goal is to allow users to set a

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

See Changes: -- [...truncated 508858 lines...] [2022-01-20T19:21:37.636Z] > Task :streams:processMessages [2022-01-20T19:21:37.636Z] Execution optimizations have been

Re: [VOTE] KIP-591: Add Kafka Streams config to set default state store

Thanks Luke! I'm +1 on the KIP. Guozhang On Wed, Jan 19, 2022 at 5:58 PM Luke Chen wrote: > Hi devs, > > I'd like to start a vote for the KIP-591: Add Kafka Streams config to set > default state store. The goal is to allow users to set a default store in > the config, so it can apply to all

Re: [DISCUSS] KIP-813 Shared State Stores

Hello Daan, Thanks for writing the KIP. I just read through it and just my 2c here: to me it seems that one of the goal would be to "externalize" the internal changelog topic of an application (say A) so that other consumers can directly read them --- though technically without any auth, anyone

Re: [VOTE] KIP-719: Deprecate Log4J Appender

Thanks for the KIP, +1 (binding). Ismael On Tue, Dec 21, 2021 at 1:00 AM Dongjin Lee wrote: > Hi All, > > I hope to reboot the voting for KIP-719: Deprecate Log4J Appender. > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-719%3A+Deprecate+Log4J+Appender > > Here is some context: the

Re: [VOTE] KIP-719: Deprecate Log4J Appender

Hi Dongjin, +1 (non-binding) many thanks Edoardo On Wed, 19 Jan 2022 at 14:07, Viktor Somogyi-Vass wrote: > Hi Dongjin, > > +1 (non-binding) from me as well. Thanks for picking this up! > > Viktor > > On Mon, Jan 17, 2022 at 1:07 PM Mickael Maison > wrote: > > > Hi Dongjin, > > > > +1

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.0 #165

See Changes: -- [...truncated 486579 lines...] [2022-01-20T15:38:07.906Z] [2022-01-20T15:38:07.906Z] SaslPlainSslEndToEndAuthorizationTest >

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

See

RE: [DISCUSS] KIP-813 Shared State Stores

Hey Matthias, Thank you for that feedback, certainly some things to think about. Let me add my thoughts: +1 on simplifying the motivation. Was aiming to add more context but I think you're right, bringing it back to the essence makes more sense. I also follow the reasoning of not having

[jira] [Created] (KAFKA-13605) Checkpoint position in state stores

Patrick Stuedi created KAFKA-13605: -- Summary: Checkpoint position in state stores Key: KAFKA-13605 URL: https://issues.apache.org/jira/browse/KAFKA-13605 Project: Kafka Issue Type:

Re: Filtering support on Fetch API

Hi, Talat, We also need the filter feature, just like apache rocketmq filter feature ( https://rocketmq.apache.org/rocketmq/filter-messages-by-sql92-in-rocketmq/). Talat Uyarer 于2021年11月30日周二 02:49写道： > Hi All, > > I want to get your advice about one subject. I want to create a KIP for >

Re: [VOTE] 3.1.0 RC1

Thanks David for running this release! I checked signatures and keys, built from source and ran unit tests with Java 11. I also ran the quickstart. +1 (binding) Thanks, Mickael On Wed, Jan 19, 2022 at 9:20 PM Bill Bejeck wrote: > > Hi David, > > Thanks for running the release! > > I did the