You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2016/09/01 08:00:37 UTC
[jira] [Resolved] (FLINK-3761) Refactor State Backends/Make Keyed
State Key-Group Aware
[ https://issues.apache.org/jira/browse/FLINK-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aljoscha Krettek resolved FLINK-3761.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0
Done in https://github.com/apache/flink/commit/4809f5367b08a9734fc1bd4875be51a9f3bb65aa
> Refactor State Backends/Make Keyed State Key-Group Aware
> --------------------------------------------------------
>
> Key: FLINK-3761
> URL: https://issues.apache.org/jira/browse/FLINK-3761
> Project: Flink
> Issue Type: Sub-task
> Components: State Backends, Checkpointing
> Reporter: Till Rohrmann
> Assignee: Aljoscha Krettek
> Fix For: 1.2.0
>
>
> After an off-line discussion with [~aljoscha], we came to the conclusion that it would be beneficial to reflect the differences between a keyed and a non-keyed stream also in the state backends. A state backend which is used for a keyed stream offers a value, list, folding and value state and has to group its keys into key groups.
> A state backend for non-keyed streams can only offer a union state to make it work with dynamic scaling. A union state is a state which is broadcasted to all tasks in case of a recovery. The state backends can then select what information they need to recover from the whole state (formerly distributed).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)