Hi Currently, Flink does not support event-time TTL state, there is an issue[1] tracking this. [1] https://issues.apache.org/jira/browse/FLINK-12005 Best, Congxian
Arti Pande <pande.a...@gmail.com> 于2020年6月17日周三 下午7:37写道： > With Flink 1.9 is state TTL supported for event-time characteristics? This > part > <https://ci.apache.org/projects/flink/flink-docs-release-1.9/dev/stream/state/state.html#state-time-to-live-ttl> > of the documentation says that > > > - > > Only TTLs in reference to *processing time* are currently supported. > > Does this mean if a program uses event-time characteristics with stateful > operators, it can not use TTL ?? > > Also clean up section > <https://ci.apache.org/projects/flink/flink-docs-release-1.9/dev/stream/state/state.html#cleanup-of-expired-state> > of > the documentation says state values that are never read will never be > cleared. > [image: Screenshot 2020-06-17 at 5.00.41 PM.png] > The question is, when processing a stream with unique elements or > keys why would Flink framework expect the same key to be read in order for > it to be removed after its expiration time ? Why does it not simply clean > up the value for that key based on timers automatically without waiting for > read operation from user code? > > Thanks > Arti >
