nielifeng commented on issue #11260: URL: https://github.com/apache/seatunnel/issues/11260#issuecomment-5139943491
I ran a fresh runtime recheck on the current `dev` revision `7e25769a8e6fa4de5f65f20fa62e0e3dcc32993c` and on PR #11271 head `4496c6e4886976ca36945642d2f997bcdcb501a9`. Test shape: - 3-master / 3-worker Zeta cluster - MySQL-CDC source with `account_histories` and `account_interests`, 10 rows each - 5-second checkpoints, parallelism 1 - take a savepoint, remove `account_interests` from the current config, then restore - write one post-restore row to the retained table and one to the removed table Current `dev` observation: - restore stayed `RUNNING` - checkpoints reached `98 triggered / 98 completed / 0 failed / 0 in progress` - the restored runtime split had `tableIds=[account_histories]`, but its `checkpointTables` and `historyTableChanges` still retained both tables - the retained-table row reached the sink (`10 -> 11`) - the removed-table row did not reach the sink (source `10 -> 11`, sink remained `10`) I intentionally kept the removed physical table present, so this run did not reproduce the exact `Can't obtain schema for table ...` exception. It did, however, confirm that stale removed-table checkpoint/history metadata remains on current `dev` after the one-table restore. PR #11271 runtime observation: - deployed head metadata was verified as `4496c6e` - restore stayed `RUNNING` - checkpoints reached `39 triggered / 39 completed / 0 failed / 0 in progress` - the restored runtime split contained only `account_histories` in `tableIds`, `checkpointTables`, and `historyTableChanges` - retained-table increment reached the sink; removed-table increment did not - no schema-restore error was present This runtime evidence supports the issue's stale-state diagnosis and confirms that #11271 closes the remaining per-table restored-state mismatch. The test cluster was returned to the default `dev` revision with zero running/pending/failed jobs after evidence collection. -- 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]
