Re: [DISCUSS] KIP-824 Allowing dumping segmentlogs limiting the batches in the output

Hi Sergio, I made a suggestion a few weeks ago about the name about the parameter but haven’t got a response for it. Did you consider it? Do we need to update the rejected alternatives section to mention the alternative options discussed in this thread? Thanks, David Le ven. 25 mars 2022 à

[VOTE] KIP-824 Allowing dumping segmentlogs limiting the batches in the output

Hi lads, I would like to start the vote on this: https://cwiki.apache.org/confluence/display/KAFKA/KIP-824%3A+Allowing+dumping+segmentlogs+limiting+the+batches+in+the+output As an extra information we are already using the patch in our company, so thanks to this patch and other extra script we

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

See Changes: -- [...truncated 484737 lines...] [2022-03-25T05:29:23.775Z] [INFO] Total time: 5.544 s [2022-03-25T05:29:23.775Z] [INFO] Finished at: 2022-03-25T05:29:23Z

Jenkins build is unstable: Kafka » Kafka Branch Builder » 2.8 #101

See

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.1 #97

See

[jira] [Resolved] (KAFKA-13770) Regression when Connect uses 0.10.x brokers due to recently added retry logic in KafkaBasedLog

[ https://issues.apache.org/jira/browse/KAFKA-13770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-13770. --- Reviewer: Konstantine Karantasis Resolution: Fixed > Regression when Connect uses

[jira] [Created] (KAFKA-13771) Support to explicitly delete delegationTokens that have expired but have not been automatically cleaned up

RivenSun created KAFKA-13771: Summary: Support to explicitly delete delegationTokens that have expired but have not been automatically cleaned up Key: KAFKA-13771 URL:

Re: [DISCUSS] KIP-824 Allowing dumping segmentlogs limiting the batches in the output

Hi Sergio, Thanks for asking. Since it's been discussed for weeks, you can start the vote anytime. Thank you. Luke On Fri, Mar 25, 2022 at 10:40 AM Sergio Troiano wrote: > Hey guys, > > > What is the next step? Who decides when it is time for voting? > > > Thanks! > > Sent from my iPhone > >

Re: [DISCUSS] KIP-824 Allowing dumping segmentlogs limiting the batches in the output

Hey guys, What is the next step? Who decides when it is time for voting? Thanks! Sent from my iPhone > On 8 Mar 2022, at 19:57, Sergio Daniel Troiano > wrote: > >  > Hi Michael, > > Yes, it's a good idea and I considered it, the main problem is the > FileRecords class does not accept

Re: [VOTE] KIP-825: introduce a new API to control when aggregated results are produced

The vote happened in the discussion thread since I started the vote there by mistake. But it passed there. To avoid having everyone vote again. I copied the content from that thread here: end of discussion thread vote == The vote passed with 5

Re: [VOTE] KIP-825: introduce a new API to control when aggregated results are produced

The vote passed with 5 binding votes from John, Guozhang, Bruno, Matthias and Bill. Thanks all for the feedback and vote. Hao On Thu, Mar 24, 2022 at 2:20 PM Bill Bejeck wrote: > Thanks for KIP Hao! > > Glad to see we settled on option 1 > > +1(binding) > > On Thu, Mar 24, 2022 at 5:13 PM

[jira] [Resolved] (KAFKA-13554) Rename RangeQuery to KeyRangeQuery

[ https://issues.apache.org/jira/browse/KAFKA-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-13554. -- Resolution: Won't Fix > Rename RangeQuery to KeyRangeQuery >

Re: [DISCUSS] KIP-819: Merge multiple KStreams in one operation

Thanks for proposing this KIP. I feel a little bit torn by the idea. In general, we try to keep the surface area small, and only add APIs that delivery (significant) value. It seems the current proposal is more or less about syntactic sugar, what can still be valuable, but I am not really

Re: [VOTE] KIP-825: introduce a new API to control when aggregated results are produced

Thanks for KIP Hao! Glad to see we settled on option 1 +1(binding) On Thu, Mar 24, 2022 at 5:13 PM Matthias J. Sax wrote: > +1 (binding) > > > On 3/24/22 1:52 PM, Hao Li wrote: > > I hit reply on my phone in the mail app and changed the title and text > > hoping it will start a new thread.

Re: [VOTE] KIP-825: introduce a new API to control when aggregated results are produced

+1 (binding) On 3/24/22 1:52 PM, Hao Li wrote: I hit reply on my phone in the mail app and changed the title and text hoping it will start a new thread. Apparently it doesn't work... On Thu, Mar 24, 2022 at 12:36 PM Bruno Cadonna wrote: Hi Hao, Actually, this is the VOTE thread. Do you

Re: [VOTE] KIP-825: introduce a new API to control when aggregated results are produced

Thanks, Hao, I’m +1 (binding) -John On Thu, Mar 24, 2022, at 11:38, Hao Li wrote: > Hi all, > > I'd like to start a vote on Kafka Streams KIP-825: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-825%3A+introduce+a+new+API+to+control+when+aggregated+results+are+produced > > Thanks, > Hao

Re: [VOTE] KIP-825: introduce a new API to control when aggregated results are produced

I hit reply on my phone in the mail app and changed the title and text hoping it will start a new thread. Apparently it doesn't work... On Thu, Mar 24, 2022 at 12:36 PM Bruno Cadonna wrote: > Hi Hao, > > Actually, this is the VOTE thread. Do you use GMail? Sometimes it is a > bit weird how it

[jira] [Created] (KAFKA-13770) Regression when Connect uses 0.10.x brokers due to recently added retry logic in KafkaBasedLog

Randall Hauch created KAFKA-13770: - Summary: Regression when Connect uses 0.10.x brokers due to recently added retry logic in KafkaBasedLog Key: KAFKA-13770 URL: https://issues.apache.org/jira/browse/KAFKA-13770

Re: [VOTE] KIP-825: introduce a new API to control when aggregated results are produced

Hi Hao, Actually, this is the VOTE thread. Do you use GMail? Sometimes it is a bit weird how it shows e-mails in threads. Anyways, thank you for the KIP and your patience! +1 (binding) Best, Bruno On 24.03.22 17:36, Hao Li wrote: Thanks John and Guozhang. Didn't realize I used this

[jira] [Resolved] (KAFKA-13692) stream thread blocked-time-ns-total metric does not include producer metadata wait time

[ https://issues.apache.org/jira/browse/KAFKA-13692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-13692. --- Fix Version/s: 3.3.0 (was: 3.2.0) Resolution: Fixed > stream

[VOTE] KIP-825: introduce a new API to control when aggregated results are produced

Hi all, I'd like to start a vote on Kafka Streams KIP-825: https://cwiki.apache.org/confluence/display/KAFKA/KIP-825%3A+introduce+a+new+API+to+control+when+aggregated+results+are+produced Thanks, Hao

Re: [VOTE] KIP-825: introduce a new API to control when aggregated results are produced

Thanks John and Guozhang. Didn't realize I used this discussion thread for voting. Let me start a new thread for voting. Will fix the KIP. On Thu, Mar 24, 2022 at 9:28 AM Guozhang Wang wrote: > +1 (binding). > > Thanks Hao! > > > Guozhang > > On Thu, Mar 24, 2022 at 9:20 AM John Roesler wrote:

Re: [VOTE] KIP-825: introduce a new API to control when aggregated results are produced

+1 (binding). Thanks Hao! Guozhang On Thu, Mar 24, 2022 at 9:20 AM John Roesler wrote: > Thanks, Hao! > > I'm +1 (binding) > > -John > > On Wed, 2022-03-23 at 22:25 -0700, Hao Li wrote: > > Hi all, > > > > I'd like to start a vote on Kafka Streams KIP-825: > > >

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.1 #96

See Changes: -- [...truncated 438822 lines...] [2022-03-24T16:18:18.008Z] > Task :clients:generatePomFileForMavenJavaPublication [2022-03-24T16:18:18.008Z]

Re: [DISCUSS] KIP-825: introduce a new API to control when aggregated results are produced

Thanks, Hao, The KIP looks good to me overall, so I'll go ahead and vote. I did notice a couple of typos, though: > static EmitStrategy onWindowClose() { > return new WindowCloseTrigger(); > } should return WindowCloseStrategy. The other strategy also references WindowUpdateTrigger, which I'm

Re: [VOTE] KIP-825: introduce a new API to control when aggregated results are produced

Thanks, Hao! I'm +1 (binding) -John On Wed, 2022-03-23 at 22:25 -0700, Hao Li wrote: > Hi all, > > I'd like to start a vote on Kafka Streams KIP-825: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-825%3A+introduce+a+new+API+to+control+when+aggregated+results+are+produced

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

See Changes: -- [...truncated 385783 lines...] [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // stage [Pipeline] } [2022-03-24T15:48:17.677Z]

[jira] [Created] (KAFKA-13769) KTable FK join can miss records if an upstream non-key-changing operation changes key serializer

Aleksandr Sorokoumov created KAFKA-13769: Summary: KTable FK join can miss records if an upstream non-key-changing operation changes key serializer Key: KAFKA-13769 URL:

Re: [DISCUSS] KIP-651 - Support PEM format for SSL certificates and

Hi all, Thanks Dejan for bringing this up. Relaxing this constraint seems reasonable to me. I guess we would have to relax it for the keystores at some point in the future as well (with Java 18). Let's wait a few days to see what others think about this. Best, David On Wed, Mar 23, 2022 at

[jira] [Resolved] (KAFKA-13128) Flaky Test StoreQueryIntegrationTest.shouldQueryStoresAfterAddingAndRemovingStreamThread

[ https://issues.apache.org/jira/browse/KAFKA-13128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-13128. --- Resolution: Fixed > Flaky Test >

Re: [VOTE] KIP-653: Upgrade log4j to log4j2

Mickael, If reload4j is fully compatible, then no vote should be needed. It would be great if a committer could review the PR, test it and verify that this is the case. For example, I noticed that the maven coordinates are not the same. What happens if both log4j and reload4j are in the

Re: [VOTE] KIP-653: Upgrade log4j to log4j2

Hi, So to summarize, it seems the plan is to: - adopt reload4j in Kafka 3.2.0 - delay the switch to log4j2 to Kafka 4.0.0 Reload4j is supposed to be a fully compatible drop-in replacement for log4j. Do we still want to do a vote for the switch? It looks like there's already a JIRA and a PR

Re: [DISCUSS] Apache Kafka 3.2.0 release

Added the jira query link for the blocker tickets that needed to help.

Re: [DISCUSS] Apache Kafka 3.2.0 release

Hi Kafkateers, we still have 16 blocker tickets and 7 critical tickets that are not resolved for AK 3.2. Out of these tickets 13 are flaky tests. Those flaky tests were disabled to not hinder further development (https://github.com/apache/kafka/pull/11895). Still we need to investigate

[jira] [Created] (KAFKA-13768) Transactional producer exits because of expiration in RecordAccumulator

xuexiaoyue created KAFKA-13768: -- Summary: Transactional producer exits because of expiration in RecordAccumulator Key: KAFKA-13768 URL: https://issues.apache.org/jira/browse/KAFKA-13768 Project: Kafka

[jira] [Created] (KAFKA-13767) consumer fetch request does not need to put to  delayFetch queue when the preferred read replica not local

zhaobo created KAFKA-13767: -- Summary: consumer fetch request does not need to put to  delayFetch queue when the preferred read replica not local Key: KAFKA-13767 URL: https://issues.apache.org/jira/browse/KAFKA-13767

Re: [VOTE] KIP-653: Upgrade log4j to log4j2

No. It is why I have no firm position. I will follow the community's decision. Thanks, Dongjin On Thu, Mar 24, 2022 at 12:34 AM Ismael Juma wrote: > Hi Dongjin, > > We really appreciate the super valuable work you've been doing here. Do we > have evidence that customers don't use custom