davidzollo commented on issue #11239: URL: https://github.com/apache/seatunnel/issues/11239#issuecomment-4874566618
> [@DanielLeens](https://github.com/DanielLeens) [@davidzollo](https://github.com/davidzollo) I have a branch ready for this. > > The change adds an `Upgrade Compatibility` workflow with manual and scheduled runs. The flow builds the current `dev` distribution, downloads the previous SeaTunnel release, creates a savepoint with the old release, then restores the same job id with current `dev`. > > I added two scenarios for the first version: > > * `generic-fake-localfile`: `FakeSource -> LocalFile`, then `Assert` checks the restored output > * `mysql-cdc-multitable-localfile`: starts MySQL 8, seeds two CDC tables, runs `MySQL-CDC -> LocalFile`, creates a savepoint on the old release, restores on `dev`, then verifies the restored output with `Assert` > > I also kept the runner scenario based, so more CDC or connector-specific restore cases can be added later without changing the workflow structure. Let me know if this looks good. Good job -- 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]
