[
https://issues.apache.org/jira/browse/FLINK-5985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926295#comment-15926295
]
ASF GitHub Bot commented on FLINK-5985:
---------------------------------------
Github user StefanRRichter commented on a diff in the pull request:
https://github.com/apache/flink/pull/3523#discussion_r106185325
--- Diff:
flink-streaming-java/src/test/java/org/apache/flink/streaming/runtime/tasks/StreamTaskTest.java
---
@@ -640,6 +640,74 @@ public SubtaskState answer(InvocationOnMock
invocation) throws Throwable {
verify(rawOperatorStateHandle).discardState();
}
+ /**
+ * FLINK-5985
+ *
+ * This test ensures that empty snapshots (no op/keyed stated
whatsoever) will be reported as stateless tasks. This
+ * happens by translating an empty {@link SubtaskState} into reporting
'null' to #acknowledgeCheckpoint.
+ */
+ @Test
+ public void testEmptySubtaskStateLeadsToStatelessAcknowledgment()
throws Exception {
--- End diff --
Yes, we could separate the classes. `CheckpointOperation` is already a
static inner class anyways. I would suggest to do this in a followup.
> Flink treats every task as stateful (making topology changes impossible)
> ------------------------------------------------------------------------
>
> Key: FLINK-5985
> URL: https://issues.apache.org/jira/browse/FLINK-5985
> Project: Flink
> Issue Type: Bug
> Components: State Backends, Checkpointing
> Affects Versions: 1.2.0
> Reporter: Gyula Fora
> Priority: Critical
>
> It seems that Flink treats every Task as stateful so changing the topology
> is not possible without setting uid on every single operator.
> If the topology has an iteration this is virtually impossible (or at least
> gets super hacky)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
