Hi vino, Thanks for the advice, but I think state TTL does not completely fit in my case.
AFAIK, State TTL is per entry level and uses an inactive time threshold to expire entries, but I need a TTL for the whole MapState, which does not depend on when the entries are created or updated. Suppose I’m calculating stats of daily active users and use a userId field as key, I want the state totally truncated at the very beginning of each day. Thanks a lot! Best, Paul Lam > 在 2018年9月14日，10:39，vino yang <yanghua1...@gmail.com> 写道： > > Hi Paul, > > Maybe you can try to understand the State TTL?[1] > > Thanks, vino. > > [1]: > https://ci.apache.org/projects/flink/flink-docs-release-1.6/dev/stream/state/state.html#state-time-to-live-ttl > > <https://ci.apache.org/projects/flink/flink-docs-release-1.6/dev/stream/state/state.html#state-time-to-live-ttl> > > Paul Lam <paullin3...@gmail.com <mailto:paullin3...@gmail.com>> 于2018年9月12日周三 > 下午6:06写道： > Hi, > > I’m using MapState to deduplicate some ids and the MapState needs to be > truncated periodically. I tried to use ProcessingTimeCallback to call > state.clear(), but in this way I can only clear the state for one key, and > actually I need a key group level cleanup. So I’m wondering is there any best > practice for my case? Thanks a lot! > > Best, > Paul Lam
