Re: BUG: eos KeyValueStore::delete() in Punctuator

I re-compiled with the current `trunk` branch and the bug was fixed. Thank you for pointing that out, Matthias, and sorry for the false alarm! Cheers, Colt McNealy *Founder, LittleHorse.io* On Mon, Dec 5, 2022 at 7:42 PM Matthias J. Sax wrote: > Thanks for reporting this issue. > > It might

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

See

Re: BUG: eos KeyValueStore::delete() in Punctuator

Thanks for reporting this issue. It might have been fixed via https://issues.apache.org/jira/browse/KAFKA-14294 already. -Matthias On 12/3/22 7:05 PM, Colt McNealy wrote: Hi all, I believe I've found a bug in Kafka Streams when: - Running an app in EOS - Calling

[jira] [Resolved] (KAFKA-14440) Local state wipeout with EOS

[ https://issues.apache.org/jira/browse/KAFKA-14440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-14440. - Resolution: Duplicate > Local state wipeout with EOS > > >

Re: [VOTE] KIP-893: The Kafka protocol should support nullable structs

+1 (binding) -- Thanks, Ziming > On Dec 6, 2022, at 10:48, John Roesler wrote: > > +1 (binding) > > Thanks, > -John > > On Mon, Dec 5, 2022, at 16:57, Kirk True wrote: >> +1 (non-binding) >> >> On Mon, Dec 5, 2022, at 10:05 AM, Colin McCabe wrote: >>> +1 (binding) >>> >>> best, >>> Colin

Re: [VOTE] KIP-893: The Kafka protocol should support nullable structs

+1 (binding) Thanks, -John On Mon, Dec 5, 2022, at 16:57, Kirk True wrote: > +1 (non-binding) > > On Mon, Dec 5, 2022, at 10:05 AM, Colin McCabe wrote: >> +1 (binding) >> >> best, >> Colin >> >> On Mon, Dec 5, 2022, at 10:03, David Jacot wrote: >> > Hi all, >> > >> > As this KIP-893 is trivial

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

See

[jira] [Created] (KAFKA-14444) Simplify user experience of customizing partitioning strategy in Streams

A. Sophie Blee-Goldman created KAFKA-1: -- Summary: Simplify user experience of customizing partitioning strategy in Streams Key: KAFKA-1 URL: https://issues.apache.org/jira/browse/KAFKA-1

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

See Changes: -- [...truncated 477860 lines...] [2022-12-05T16:34:37.477Z] [2022-12-05T16:34:37.477Z] Gradle Test Run :streams:integrationTest > Gradle Test Executor 168

[jira] [Resolved] (KAFKA-14398) Update EndToEndAuthorizerTest.scala to test with ZK and KRAFT quorum servers

[ https://issues.apache.org/jira/browse/KAFKA-14398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Proven Provenzano resolved KAFKA-14398. --- Resolution: Resolved > Update EndToEndAuthorizerTest.scala to test with ZK and

Re: [DISCUSS] Apache Kafka 3.4.0 release

Hi All, Just notifying everyone of a regression introduced by KIP-787, currently only present on trunk, but which may qualify as a blocker for the release. It manifests as a moderate resource leak on MirrorMaker2 clusters. The fix should have a small scope and low risk. Here's the bug ticket:

Re: Supported Kafka/Zookeeper Version with ELK 8.4.3

Hi All, Well this question can be asked on discuss.elastic.co However I would like to answer this. I am sure you need compatibility with logstash. You can go through this document for logstash-kafka integration https://www.elastic.co/guide/en/logstash/current/plugins-integrations-kafka.html

[jira] [Created] (KAFKA-14443) Mirror Maker Connectors leak admin clients used for topic creation

Greg Harris created KAFKA-14443: --- Summary: Mirror Maker Connectors leak admin clients used for topic creation Key: KAFKA-14443 URL: https://issues.apache.org/jira/browse/KAFKA-14443 Project: Kafka

Re: [VOTE] KIP-893: The Kafka protocol should support nullable structs

+1 (binding) best, Colin On Mon, Dec 5, 2022, at 10:03, David Jacot wrote: > Hi all, > > As this KIP-893 is trivial and non-controversial, I would like to > start the vote on it. The KIP is here: > https://cwiki.apache.org/confluence/x/YJIODg > > Thanks, > David

Re: Ci stability

Thanks Colin, I have a draft PR open which I occasionally check on and disable the failing tests, I'll update it and see if it passes. Thanks, Daniel Scanteianu On Mon, Dec 5, 2022, 18:02 Colin McCabe wrote: > FYI, there was a memory leak that affected some of the tests which was > fixed

[VOTE] KIP-893: The Kafka protocol should support nullable structs

Hi all, As this KIP-893 is trivial and non-controversial, I would like to start the vote on it. The KIP is here: https://cwiki.apache.org/confluence/x/YJIODg Thanks, David

Re: Supported Kafka/Zookeeper Version with ELK 8.4.3

Hi, Sorry, we do not develop ELK. In fact, I'm not sure what that acronym refers to. I would suggest checking in with support for that product / project, since it is not part of Apache Kafka. best, Colin On Fri, Oct 28, 2022, at 06:23, Kumar, Sudip wrote: > Hi Team, > > We are still

Re: Ci stability

FYI, there was a memory leak that affected some of the tests which was fixed recently, so hopefully stability will improve a bit. See KAFKA-14433 for details. best, Colin On Thu, Nov 24, 2022, at 12:48, John Roesler wrote: > Hi Dan, > > I’m not sure if there’s a consistently used tag, but I’ve

Re: [DISCUSS] KIP-893: The Kafka protocol should support nullable structs

Hi David, Thanks for posting this. I think it will be pretty useful. +1 for the idea best, Colin On Thu, Dec 1, 2022, at 08:57, David Jacot wrote: > Hi all, > > I have drafted a very small KIP which proposes to support nullable > struct in the Kafka protocol. This is something that we plan to

Re: Plase add me as a contributor to JIRA

Hi, I've granted you contributor permissions. Thanks for your interest in Apache Kafka! Mickael On Mon, Dec 5, 2022 at 4:31 PM Pie Land wrote: > > Hello, > > Please add me as a contributor to JIRA. > My JIRA username is: cookpieland > > Thanks, > Cook

Re: [DISCUSS] KIP-883: Add delete callback method to Connector API

Hi Hector, Thanks for the updates! RE 1: This doesn't have the same user-facing behavior, though. Today failures in Connector::stop can be surfaced via the status endpoints in the REST API. But when connectors are deleted, they won't be visible at all in these endpoints. RE 3: It seems like

Plase add me as a contributor to JIRA

Hello, Please add me as a contributor to JIRA. My JIRA username is: cookpieland Thanks, Cook

Re: [DISCUSS] KIP-864: Add End-To-End Latency Metrics to Connectors

Hi Jorge, Thanks for indulging my paranoia. LGTM! Cheers, Chris On Mon, Dec 5, 2022 at 10:06 AM Jorge Esteban Quilcate Otoya < quilcate.jo...@gmail.com> wrote: > Sure! I have a added the following to the proposed changes section: > > ``` > The per-record metrics will definitely be added to

Re: [DISCUSS] KIP-864: Add End-To-End Latency Metrics to Connectors

Sure! I have a added the following to the proposed changes section: ``` The per-record metrics will definitely be added to Kafka Connect as part of this KIP, but their metric level will be changed pending the performance testing described in KAFKA-14441, and will otherwise only be exposed at

Re: [DISCUSS] KIP-864: Add End-To-End Latency Metrics to Connectors

Hi Jorge, Thanks for filing KAFKA-14441! In the ticket description we mention that "there will be more confidence whether to design metrics to be exposed at a DEBUG or INFO level depending on their impact" but it doesn't seem like this is called out in the KIP and, just based on what's in the

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

See

[jira] [Created] (KAFKA-14442) GlobalKTable restoration waits requestTimeout during application restart

Gergo L��p created KAFKA-14442: -- Summary: GlobalKTable restoration waits requestTimeout during application restart Key: KAFKA-14442 URL: https://issues.apache.org/jira/browse/KAFKA-14442 Project: Kafka

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

See