[ 
https://issues.apache.org/jira/browse/FLINK-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16424206#comment-16424206
 ] 

ASF GitHub Bot commented on FLINK-5480:
---------------------------------------

Github user zentol commented on the issue:

    https://github.com/apache/flink/pull/3117
  
    @ShashwatRastogi-Reflektion It's a bit odd that there are different ID's 
shown, I will have to look into that. It may be that one display accounts for 
the uid while the other one doesn't; in any case one of them should be the task 
ID.
    
    I should've asked earlier; which version of Flink are you using?
    
    If it is 1.2 or below, then I don't know at the moment what the problem 
could be.
    If it is 1.3 or above, the steps I mentioned have to be done for each 
operator, and not task. That said, I'm not sure if we actually expose the id of 
each operator anywhere in 1.3 in a nice way... You may have to resort to 
trial&error; if a state can't be assigned to an operator you should get an 
exception containing the ID of the state (unless you explicitly allow 
[non-restored 
state](https://ci.apache.org/projects/flink/flink-docs-master/ops/state/savepoints.html#allowing-non-restored-state),
 which you can then use as the uid hash. If you are already on 1.4 you can 
figure them out with the metric system (for example with the JMXReporter).


> 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
>            Priority: Major
>             Fix For: 1.2.0, 1.3.0
>
>
> 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
(v7.6.3#76005)

Reply via email to