Hi Anchit,
the timers don't necessarily have to be cleaned up. So you should be good
to go.
Cheers,
Aljoscha
On Fri, 28 Oct 2016 at 23:33 Anchit Jatana
wrote:
> Hi Aljoscha,
>
> I am using the custom trigger with GlobalWindows window assigner. Do I
> still
> need
Hi Aljoscha,
I am using the custom trigger with GlobalWindows window assigner. Do I still
need to override clear method and delete the ProcessingTimeTimer using-
triggerContext.deleteProcessingTimeTimer(prevTime)?
Regards,
Anchit
--
View this message in context:
Hi Bart,
are you using your custom Trigger together with a merging session window
assigner?
You might want to consider overriding the clear() method in your trigger to
clean up the state that you use. If you don't you might run into memory
leaks because the state is never cleaned up.
Cheers,
Hi Bart,
Thank you so much for sharing the approach. Looks like this solved my
problem. Here's what I have as an implementation for my use-case:
package org.apache.flink.quickstart
import org.apache.flink.api.common.state.{ ReducingState,
ReducingStateDescriptor, ValueState,