[ https://issues.apache.org/jira/browse/FLINK-16638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093203#comment-17093203 ]
Roman Khachatryan commented on FLINK-16638: ------------------------------------------- Hi [~edu05], Thanks a lot for offering your help! Can you please describe the second approach that you mentioned? > Flink checkStateMappingCompleteness doesn't include UserDefinedOperatorIDs > -------------------------------------------------------------------------- > > Key: FLINK-16638 > URL: https://issues.apache.org/jira/browse/FLINK-16638 > Project: Flink > Issue Type: Bug > Components: Runtime / Checkpointing > Affects Versions: 1.9.1, 1.10.0 > Reporter: Bashar Abdul Jawad > Priority: Critical > Fix For: 1.11.0 > > > [StateAssignmentOperation.checkStateMappingCompleteness|https://github.com/apache/flink/blob/master/flink-runtime/src/main/java/org/apache/flink/runtime/checkpoint/StateAssignmentOperation.java#L555] > doesn't check for UserDefinedOperatorIDs (specified using setUidHash), > causing the exception: > {code} > java.lang.IllegalStateException: There is no operator for the state {} > {code} > to be thrown when a savepoint can't be mapped to an ExecutionJobVertex, even > when the operator hash is explicitly specified. > I believe this logic should be extended to also include > UserDefinedOperatorIDs as so: > {code:java} > for (ExecutionJobVertex executionJobVertex : tasks) { > allOperatorIDs.addAll(executionJobVertex.getOperatorIDs()); > allOperatorIDs.addAll(executionJobVertex.getUserDefinedOperatorIDs()); > } > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)