Hi Ori, I guess you consume from Kafka from the earliest offset, so you consume historical data and Flink is catching-up.
Regarding: *My event-time timestamps also do not have big gaps* Just to verify, if you do keyBy sessionId, do you check the gaps of events from the same session? Rafi On Tue, Jun 16, 2020 at 9:36 AM Ori Popowski <ori....@gmail.com> wrote: > So why is it happening? I have no clue at the moment. > My event-time timestamps also do not have big gaps between them that would > explain the window triggering. > > > On Mon, Jun 15, 2020 at 9:21 PM Robert Metzger <rmetz...@apache.org> > wrote: > >> If you are using event time in Flink, it is disconnected from the real >> world wall clock time. >> You can process historical data in a streaming program as if it was >> real-time data (potentially reading through (event time) years of data in a >> few (wall clock) minutes) >> >> On Mon, Jun 15, 2020 at 4:58 PM Yichao Yang <1048262...@qq.com> wrote: >> >>> Hi >>> >>> I think it maybe you use the event time, and the timestamp between your >>> event data is bigger than 30minutes, maybe you can check the source data >>> timestamp. >>> >>> Best, >>> Yichao Yang >>> >>> ------------------------------ >>> 发自我的iPhone >>> >>> >>> ------------------ Original ------------------ >>> *From:* Ori Popowski <ori....@gmail.com> >>> *Date:* Mon,Jun 15,2020 10:50 PM >>> *To:* user <user@flink.apache.org> >>> *Subject:* Re: EventTimeSessionWindow firing too soon >>> >>>
