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

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

Github user ShashwatRastogi-Reflektion commented on the issue:

    https://github.com/apache/flink/pull/3117
  
    Hey @zentol 
    
    Thank you for replying back. I was trying to do exactly the same thing, but 
I think I am messing something up that is why it isn't working in my case.
    
    In my logs, i get the task description like:
    `2018-04-03 12:24:45,876 INFO  
org.apache.flink.runtime.executiongraph.ExecutionGraph        - Source: Custom 
Source -> Filter -> events-with-timestamp -> filtered-events-with-timestamp -> 
events-mapped-to-session (1/1) (5c69d4ad31a844978a740c1d24297b68) switched from 
CREATED to SCHEDULED.` Is the hash present in this log statement called uid 
hash? 
    
    This hash is not the same which I get in the UI.
    
![image](https://user-images.githubusercontent.com/29359103/38256652-6a5e7d58-377c-11e8-8124-16bc2cd7e6e0.png)
    
    I have tried using both and both of them doesn't work.
    
    Also, my operators are chained together so I will get one uid-hash for the 
entire chain, right?
    And, I would be setting the same uid-hash for all operators in the chain?


> 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