SEZ9 commented on issue #12382: URL: https://github.com/apache/seatunnel/issues/12382#issuecomment-5852088443
@xinnyuli, thanks for taking this on. The comparison boundary is the failing scheduled run (https://github.com/apache/seatunnel/actions/runs/35244548330/job/105282609961, `dev` commit `c7304ace6e18d350314e92480df1fd3c0962f1f2`) versus current `dev` including `5af8d789aa9ae3d94df4a9cc0f03cee3c0a6d0e6`. When you have results, could you post back with: 1. the reproduction rate of the `id=15` restore assertion at each of those two revisions, with the exact revision tested recorded; and 2. if it does reproduce, which of the three boundaries the row goes missing at (`PostgresWalFetchTask` handoff, reader emission/checkpoint-offset advancement, or JDBC-sink receipt/commit), using test-only, correlation-safe evidence. If it does not reproduce with the real Zeta savepoint -> restore -> post-reattachment sequence at either revision, please say so explicitly. That result will decide the next step; until then, no production-fix PR or production tracing is needed. <!-- streview-comment:1351 --> -- 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]
