sangkyoonnam opened a new issue, #1332: URL: https://github.com/apache/flink-agents/issues/1332
### Search before asking - [x] I searched in the [issues](https://github.com/apache/flink-agents/issues) and found nothing similar. ### Description `ActionExecutionOperator` has no test that restores state written by an earlier release. In local operator-harness runs, snapshots taken while an action was pending failed to restore on both upgrade paths I tried, 0.2.1 to 0.3.0 and 0.3.0 to 0.4.0-rc1. The results and the upgrade policy questions are in #1327. I'd like to add migration tests modeled on Flink's `MigrationTest` (`WindowOperatorMigrationTest`, `CEPMigrationTest`), with a flink-agents version enum in place of `FlinkVersion`, which can't name agents releases: - A snapshot generator and a `generate-migration-test-data` profile in `runtime`, so a release can commit versioned reference snapshots, following Flink's practice. - `ActionExecutionOperatorMigrationTest`, parameterized over the committed versions and starting with state at rest. It would check that short-term memory, the per-key sequence number and the persisted job identifier keep their saved values, that pending state is empty, and that processing continues after restore. The test uses its own agent whose actions stay fixed across releases. - A reference snapshot generated from the released 0.4.0. Committing it doesn't decide whether 0.4 state must restore on 1.0; that stays with #1327. This is test infrastructure only, with no production code changes, and the first scenario doesn't cover the pending-action failures. Other scenarios and any serializer changes would be separate issues once #1327 settles the guarantee. ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- 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]
