[
https://issues.apache.org/jira/browse/FLINK-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16544256#comment-16544256
]
ASF GitHub Bot commented on FLINK-9489:
---------------------------------------
Github user sihuazhou commented on a diff in the pull request:
https://github.com/apache/flink/pull/6333#discussion_r202516863
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/state/KeyGroupPartitioner.java
---
@@ -264,6 +265,42 @@ public void writeMappingsInKeyGroup(@Nonnull
DataOutputView dov, int keyGroupId)
}
}
+ public static <T> StateSnapshotKeyGroupReader
createKeyGroupPartitionReader(
+ @Nonnull ElementReaderFunction<T> readerFunction,
+ @Nonnull KeyGroupElementsConsumer<T> elementConsumer) {
+ return new PartitioningResultKeyGroupReader<>(readerFunction,
elementConsumer);
+ }
+
+ /**
+ * General algorithm to read key-grouped state that was written from a
{@link PartitioningResult}
+ * @param <T>
--- End diff --
description for `T` is missing.
> Checkpoint timers as part of managed keyed state instead of raw keyed state
> ---------------------------------------------------------------------------
>
> Key: FLINK-9489
> URL: https://issues.apache.org/jira/browse/FLINK-9489
> Project: Flink
> Issue Type: Sub-task
> Components: State Backends, Checkpointing
> Reporter: Stefan Richter
> Assignee: Stefan Richter
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
>
> Timer state should now become part of the keyed state backend snapshot, i.e.,
> stored inside the managed keyed state. This means that we have to connect our
> preparation for asynchronous checkpoints with the backend, so that the timers
> are written as part of the state for each key-group. This means that we will
> also free up the raw keyed state an might expose it to user functions in the
> future.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
