You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stefan Richter (JIRA)" <ji...@apache.org> on 2018/06/01 12:50:00 UTC
[jira] [Assigned] (FLINK-9486) Introduce TimerState in keyed state
backend
[ https://issues.apache.org/jira/browse/FLINK-9486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Richter reassigned FLINK-9486:
-------------------------------------
Assignee: Stefan Richter
> Introduce TimerState in keyed state backend
> -------------------------------------------
>
> Key: FLINK-9486
> URL: https://issues.apache.org/jira/browse/FLINK-9486
> Project: Flink
> Issue Type: Sub-task
> Components: State Backends, Checkpointing
> Reporter: Stefan Richter
> Assignee: Stefan Richter
> Priority: Major
> Fix For: 1.6.0
>
>
> This is the first implementation subtask.
> Goal of this PR is to introduce a timer state that is registered with the keyed state backend, similar to other forms of keyed state.
> For the {{HeapKeyedStateBackend}}, this state lives on the same level as the {{StateTable}} that hold other forms of keyed state, and the implementation is basically backed by {{InternalTimerHeap}}.
> For {{RocksDBKeyedStateBackend}}, in this first step, we also introduce this state, outside of RocksDB and based upon {{InternalTimerHeap}}. This is an intermediate state, and we will later also implement the alternative to store the timers inside a column families in RocksDB. However, by taking this step, we could also still offer the option to have RocksDB state with heap-based timers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)