Re: Fast and slow stream sources for Interval Join

2023-02-27 Thread Alexis Sarda-Espinosa
Hi Mason, Very interesting, is it possible to apply both types of alignment? I.e., considering watermark skew across splits from within one source & also from another source? Regards, Alexis. On Tue, 28 Feb 2023, 05:26 Mason Chen, wrote: > Hi all, > > It's true that the problem can be handled

Re: unsubscribe

2023-02-27 Thread Hang Ruan
Hi, please send to user-unsubscr...@flink.apache.org if you want to unsubscribe user mail list. Best, Hang zhangjunjie 于2023年2月28日周二 00:11写道: > unsubscribe > > >

Re: unsubscribe

2023-02-27 Thread weijie guo
To unsubscribe, please send an email to user-unsubscr...@flink.apache.org Best regards, Weijie Natia Chachkhiani 于2023年2月28日周二 01:21写道: >

Re: Fast and slow stream sources for Interval Join

2023-02-27 Thread Mason Chen
Hi all, It's true that the problem can be handled by caching records in state. However, there is an alternative using `watermark alignment` with Flink 1.15+ [1] which does the desired synchronization that you described while reducing the size of state from the former approach. To use this with tw

unsubscribe

2023-02-27 Thread Natia Chachkhiani

Re: Fast and slow stream sources for Interval Join

2023-02-27 Thread Alexis Sarda-Espinosa
Hello, I had this question myself and I've seen it a few times, the answer is always the same, there's currently no official way to handle it without state. Regards, Alexis. On Mon, 27 Feb 2023, 14:09 Remigiusz Janeczek, wrote: > Hi, > > How to handle a case where one of the Kafka topics used

unsubscribe

2023-02-27 Thread zhangjunjie
unsubscribe

Fast and slow stream sources for Interval Join

2023-02-27 Thread Remigiusz Janeczek
Hi, How to handle a case where one of the Kafka topics used for interval join is slower than the other? (Or a case where one topic lags behind) Is there a way to stop consuming from the fast topic and wait for the slow one to catch up? I want to avoid running out of memory (or keeping a very larg

unsubscribe

2023-02-27 Thread Sandeep Sharat
unsubscribe -- Thanks & Regards Sandeep Sharat Kumar

Re: RE: Re: Re: Should we always mark ValueState as "transient" forRichFunctions

2023-02-27 Thread Shammon FY
Hi I think there is no benchmark about this at present Best, Shammon On Sun, Feb 26, 2023 at 5:49 PM Gen Luo wrote: > Hi, > > I suppose there are two things to clarify: > 1. the function object will only be serialized once when deploying and > deserialized once per task while initializing. > 2