XComp commented on PR #21736: URL: https://github.com/apache/flink/pull/21736#issuecomment-1458103927
Yeah, one option would be to use a constant variable. The RM would need to update that one along generating the test data. A minor thing: The variable should be named `MOST_RECENTLY_PUBLISHED_VERSION`. Considering that this is only used by the migration test, we could even move this constant into `MigrationTestsSnapshotGenerator`. Alternatively, we could write this information into a metadata file that's located in the `flink-migration-test-utils` sub-module's resources and update that file as part of the `MigrationTestsSnapshotGenerator` test run. The user has to specify the version as part of this run, anyway. Therefore, there's no need for an additional change of code manually. -- 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]
