Github user StefanRRichter commented on the issue:
https://github.com/apache/flink/pull/6062
@sihuazhou This is exactly my plan on how introduce a "timer state" for the
keyed state backends. In a nutshell, time timer service can just register and
operator on those states, where the basic operations that we expose are
somewhat along the lines of `scheduleTimer`, `stopTimer`, `peekNextTimer`,
`pollNextTimer`. I am currently working on a small design document to outline
this integration. For RocksDB we can implementation of the state can be loosely
based on some of the ideas from the class `RocksDBTimerHeap` of PR #3359.
---