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

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

GitHub user StefanRRichter opened a pull request:

    https://github.com/apache/flink/pull/3117

    [FLINK-5480] Introduce user-provided hash for JobVertexes

    This PR allows 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.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/StefanRRichter/flink UserProvidedHash

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/3117.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3117
    
----
commit 96ef2c041bfe33462600d72b8ec1472f53c852f2
Author: Stefan Richter <s.rich...@data-artisans.com>
Date:   2017-01-12T17:57:52Z

    [FLINK-5480] Introduce user-provided hash for JobVertexes

----


> 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)

Reply via email to