Hi, If you use tumbling windows or sliding windows then Flink will not keep additional meta data besides the actual window contents. Also, if you use a Trigger that purges when firing Flink will clean the window contents after firing a window. This means that you can set allowed lateness to MAX and always process all late-arriving events without keeping any state. Of course, when processing those late events you will get a window that only contains that event, not the complete window that was already processed and purged before.
Best, Aljoscha > On 22. May 2017, at 21:51, rhashmi <rizhas...@hotmail.com> wrote: > > Could you elaborate this more? If i assume if i set window time to max .. > does it mean my window will stay for infinite time framework, > Wouldn't this may hit memory overflow with time? > > > > > -- > View this message in context: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/State-in-Custom-Tumble-Window-Class-tp13177p13255.html > Sent from the Apache Flink User Mailing List archive. mailing list archive at > Nabble.com.
