[
https://issues.apache.org/jira/browse/FLINK-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834642#comment-15834642
]
ASF GitHub Bot commented on FLINK-5480:
---------------------------------------
Github user uce commented on the issue:
https://github.com/apache/flink/pull/3117
Thanks! Looks good. Just tested this with a job where I did not set any
UIDs. After changing in an incompatible way (with respect to auto generated
IDs) I was able to restore my state with `setUidHash`. I further played around
with it by adding a completely new operator, which also restored the state of
an operator in addition to the regular one. I think this will be very powerful
once we provide some less low level plumbing around it. The biggest pain point
right now (independent of this PR) is figuring out the old IDs.
I will go ahead and merge this for `master` and `release-1.2`.
> User-provided hashes for operators
> ----------------------------------
>
> Key: FLINK-5480
> URL: https://issues.apache.org/jira/browse/FLINK-5480
> Project: Flink
> Issue Type: Improvement
> Components: DataStream API
> Affects Versions: 1.2.0
> Reporter: Stefan Richter
> Assignee: Stefan Richter
>
> We could allow users to provided (alternative) hashes for operators in a
> StreamGraph. This can make migration between Flink versions easier, in case
> the automatically produced hashes between versions are incompatible. For
> example, users could just copy the old hashes from the web ui to their job.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
