xintongsong commented on pull request #17403: URL: https://github.com/apache/flink/pull/17403#issuecomment-939739016
I wonder if we can make the `MigrationVersion` updates easier, and reduce the chance of making mistakes. 1. Instead of manually going through all places where `MigrationVersion` is used, we may consider something like `MigrationVersion#versionListSince(MigrationVersion sinceVersion)`, so that we won't need to update the list of versions for each relevant test. 2. I wonder if there's a way to simply regeneration of the migration tests files. E.g., a script or maven profile that executes all test cases / methods with a specific annotation. This for sure can be a separate effort and should not block this PR from merging. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
