Hi, thanks for letting us know! And sorry that you didn’t get any response from the community, I myself just got back from vacation so I’m only now catching up on mail.
Best, Aljoscha > On 30. Mar 2017, at 18:24, Andrea Spina <andrea.sp...@radicalbit.io> wrote: > > Dear community, > > I finally solved the issue i was bumped into. > Basically the reason of the encountered problem was the behavior of my > input: incoming rates were so far different in behavior (really late and > scarce presence of second type event in event time). > > The solution I employed was to assign timestamps and watermarks to the > source stream just before splitting it into my first type and second type > handled streams. I suppose this solved my problem due to EventTimeTrigger > .getCurrentWatermark() method, which I think it returns the minimum > watermark between the streams scoped by the TriggerContext. So the window > was hanging because of the incoming rate behavior of the second type stream. > > Hope it could help someone in the future. > > Cheers, > > Andrea > > > > -- > View this message in context: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Cogrouped-Stream-never-triggers-tumbling-event-time-window-tp12373p12468.html > Sent from the Apache Flink User Mailing List archive. mailing list archive at > Nabble.com.
