[
https://issues.apache.org/jira/browse/FLINK-5985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901040#comment-15901040
]
Ufuk Celebi commented on FLINK-5985:
------------------------------------
I fully agree that this whole UID business is very tricky and intransparent
right now.
Could you:
1) Post the Exception you get
2) Run the job before the savepoint with DEBUG logging for
org.apache.flink.streaming.api.graph
3) Run the job with which you want to restore with DEBUG logging for
org.apache.flink.streaming.api.graph?
Either this is a bug or we are overlooking a stateful task that does not have a
UID set. You can set a UID after the fact with 1.2 via `setUIDHash` to the
String of the JobVertexID.
> 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)
