[ https://issues.apache.org/jira/browse/FLINK-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940151#comment-15940151 ]
ASF GitHub Bot commented on FLINK-6034: --------------------------------------- Github user StefanRRichter commented on a diff in the pull request: https://github.com/apache/flink/pull/3531#discussion_r107877948 --- Diff: flink-streaming-java/src/main/java/org/apache/flink/streaming/api/operators/OperatorSnapshotResult.java --- @@ -30,7 +31,7 @@ */ public class OperatorSnapshotResult { - private RunnableFuture<KeyGroupsStateHandle> keyedStateManagedFuture; + private RunnableFuture<KeyedStateHandle> keyedStateManagedFuture; private RunnableFuture<KeyGroupsStateHandle> keyedStateRawFuture; --- End diff -- I think this generic type can also be changed to the higher-level interface `RunnableFuture<KeyedStateHandle>`. > Add KeyedStateHandle for the snapshots in keyed streams > ------------------------------------------------------- > > Key: FLINK-6034 > URL: https://issues.apache.org/jira/browse/FLINK-6034 > Project: Flink > Issue Type: Sub-task > Components: State Backends, Checkpointing > Reporter: Xiaogang Shi > Assignee: Xiaogang Shi > > Currently, the only type of the snapshots in keyed streams is > {{KeyGroupsStateHandle}} which is full and store the states one group after > another. With the introduction of incremental checkpointing, we need a higher > level abstraction of keyed snapshots to allow flexible snapshot formats. > The implementation of {{KeyedStateHandle}} s may vary a lot in different > backends. The only information needed in {{KeyedStateHandle}} s is their key > group range. When recovering the job with a different degree of parallelism, > {{KeyedStateHandle}} s will be assigned to those subtasks whose key group > ranges overlap with their ranges. -- This message was sent by Atlassian JIRA (v6.3.15#6346)