[
https://issues.apache.org/jira/browse/FLINK-13613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013338#comment-17013338
]
vinoyang commented on FLINK-13613:
----------------------------------
bq. Not sure whether it makes sense to move all migration tests into the same
module.
What I mean about "centralized place" not always one module. It may be several
submodules belongs to one parent module named {{flink-migration-tests}} just
like those modules under {{flink-end-to-end-tests}}. So I said:
bq. However, It would also introduce another problem: there would be many new
modules.
It has some obvious pros:
* centralized management, currently, only little people know the context of
those migration tests, they only know more via those umbrella issues(e.g. this
one), every time when the community release major version, we must list all the
class names of migration tests;
* extract common logic and introduce common modules like what you said, the
centralized mechanism can make it easier;
* towards next plan (e.g. automatic testing), currently, these migration test
belongs to different modules(some of them are first-level, others are
second-level), unify them and reorganize them may make it easier;
> 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)
