SEZ9 commented on PR #12454: URL: https://github.com/apache/seatunnel/pull/12454#issuecomment-5987426006
Thanks @xinnyuli for the before/after run linked in `5978110950`. 3/30 missing on the base vs 0/28 on this head, with id=15 starting exactly at the stored commit-end LSN in every missing run and being filtered as already processed, is exactly the boundary the PostgreSQL CDC part of this PR targets, and the runs that hit the same boundary now resuming at the stored LSN and delivering the row is the intended behavior. One small question so the evidence and the head line up: were the "after" runs executed against `3080371ce733` (the head referenced in my merge-readiness ping above), or an earlier head? If it was an earlier one, a note on which head would help whoever does the final review. Otherwise nothing has changed on my side since the ping — the current recovery / PostgreSQL CDC LSN scope still stands as-is. <!-- streview-comment:1527 --> -- 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]
