DanielLeens commented on PR #11103: URL: https://github.com/apache/seatunnel/pull/11103#issuecomment-4957122418
Thanks for the careful rereview. I rechecked the same unchanged head against the current Zeta barrier path again. On the runtime path Daniel traced before, `SinkFlowLifeCycle.received(...)` handles the barrier on the task thread and calls `writer.prepareCommit(barrierId)` and then `writer.snapshotState(barrierId)` before the next record is processed, so on this concrete file-sink fix I still do not see a reopened engine-side interleaving window on the current revision. If a new head changes the lifecycle wiring or the synchronization scope again, I am happy to revisit it. On this unchanged version, Daniel's source-side conclusion is still the same as the previous approval thread. -- 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]
