[
https://issues.apache.org/jira/browse/FLINK-8992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456095#comment-16456095
]
ASF GitHub Bot commented on FLINK-8992:
---------------------------------------
Github user tzulitai commented on a diff in the pull request:
https://github.com/apache/flink/pull/5925#discussion_r184619113
--- Diff:
flink-end-to-end-tests/flink-datastream-allround-test/src/main/java/org/apache/flink/streaming/tests/SemanticsCheckMapper.java
---
@@ -21,17 +21,15 @@
import org.apache.flink.api.common.functions.RichFlatMapFunction;
import org.apache.flink.api.common.state.ValueState;
import org.apache.flink.api.common.state.ValueStateDescriptor;
-import org.apache.flink.runtime.state.FunctionInitializationContext;
-import org.apache.flink.runtime.state.FunctionSnapshotContext;
-import org.apache.flink.streaming.api.checkpoint.CheckpointedFunction;
+import org.apache.flink.configuration.Configuration;
import org.apache.flink.util.Collector;
import java.io.Serializable;
/**
* This mapper validates exactly-once and at-least-once semantics in
connection with {@link SequenceGeneratorSource}.
*/
-public class SemanticsCheckMapper extends RichFlatMapFunction<Event,
String> implements CheckpointedFunction {
+public class SemanticsCheckMapper extends RichFlatMapFunction<Event,
String> {
--- End diff --
Actually the changes here in this file are not strictly required for
exactly-once.
I only changed this as part of trying some things out.
Can revert this if you prefer, @StefanRRichter.
> Implement source and operator that validate exactly-once
> --------------------------------------------------------
>
> Key: FLINK-8992
> URL: https://issues.apache.org/jira/browse/FLINK-8992
> Project: Flink
> Issue Type: Sub-task
> Components: Tests
> Affects Versions: 1.5.0
> Reporter: Stefan Richter
> Assignee: Stefan Richter
> Priority: Major
>
> We can build this with sources that emit sequences per key and a stateful
> (keyed) operator that validate for the update of each key that the new value
> is the old value + 1. This can help to easily detect if events/state were
> lost or duplicates.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
