[
https://issues.apache.org/jira/browse/FLINK-36058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rodrigo Meneses updated FLINK-36058:
------------------------------------
Description:
OperatorTestHarness last completed checkpoint for recovery is always reset to 0.
This looks like a known limitation:
[https://github.com/apache/flink/blob/master/flink-streaming-java/src/test/java/org/apache/flink/streaming/runtime/operators/sink/CommitterOperatorTestBase.java#L184]
By fixing this issue, users will be able to use a checkpointId different from
zero in their state recovery unit tests.
was:
OperatorTestHarness last completed checkpoint for recovery is always reset to 0.
This looks like a known limitation:
[https://github.com/apache/flink/blob/master/flink-streaming-java/src/test/java/org/apache/flink/streaming/runtime/operators/sink/CommitterOperatorTestBase.java#L223]
By fixing this issue, users will be able to use a checkpointId different from
zero in their state recovery unit tests.
> OperatorTestHarness is always using checkpointId=0 for state recovery
> ---------------------------------------------------------------------
>
> Key: FLINK-36058
> URL: https://issues.apache.org/jira/browse/FLINK-36058
> Project: Flink
> Issue Type: Improvement
> Components: Test Infrastructure, Tests
> Reporter: Rodrigo Meneses
> Priority: Major
>
> OperatorTestHarness last completed checkpoint for recovery is always reset to
> 0.
> This looks like a known limitation:
> [https://github.com/apache/flink/blob/master/flink-streaming-java/src/test/java/org/apache/flink/streaming/runtime/operators/sink/CommitterOperatorTestBase.java#L184]
>
> By fixing this issue, users will be able to use a checkpointId different from
> zero in their state recovery unit tests.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
