You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/04/12 02:01:00 UTC

[jira] [Updated] (FLINK-8978) End-to-end test: Job upgrade

     [ https://issues.apache.org/jira/browse/FLINK-8978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann updated FLINK-8978:
---------------------------------
    Fix Version/s:     (was: 1.5.0)
                   1.5.1
                   1.6.0

> End-to-end test: Job upgrade
> ----------------------------
>
>                 Key: FLINK-8978
>                 URL: https://issues.apache.org/jira/browse/FLINK-8978
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Tests
>    Affects Versions: 1.5.0
>            Reporter: Till Rohrmann
>            Priority: Blocker
>             Fix For: 1.6.0, 1.5.1
>
>
> Job upgrades usually happen during the lifetime of a real world Flink job. Therefore, we should add an end-to-end test which exactly covers this scenario. I suggest to do the follwoing:
> # run the general purpose testing job FLINK-8971
> # take a savepoint
> # Modify the job by introducing a new operator and changing the order of others
> # Resume the modified job from the savepoint
> # Verify that everything went correctly



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)