[
https://issues.apache.org/jira/browse/FLINK-13613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012537#comment-17012537
]
vinoyang commented on FLINK-13613:
----------------------------------
bq. So we can proceed with corresponding versions of subtasks 1-17 of this
issue.
So can I create an umbrella issue to track the migration from 1.9 to 1.10?
[~aljoscha]
And can we try to move and collapse all migration IT test cases into a
centralized place, a little like {{flink-end-to-end-tests}}? It would be more
focused and convenient to implement the next plan.
> Update state migration tests for Flink 1.9
> ------------------------------------------
>
> Key: FLINK-13613
> URL: https://issues.apache.org/jira/browse/FLINK-13613
> Project: Flink
> Issue Type: Task
> Components: Tests
> Affects Versions: 1.10.0
> Reporter: Till Rohrmann
> Assignee: Aljoscha Krettek
> Priority: Blocker
> Fix For: 1.10.0
>
>
> Once the Flink {{1.9.0}} release is out, we should update existing migration
> tests to cover restoring from {{1.9.0}} savepoints.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
