DanielLeens commented on PR #11231: URL: https://github.com/apache/seatunnel/pull/11231#issuecomment-4880665142
Thanks for the update. I rechecked the latest head from the Kafka exactly-once startup path again. ## Current state on the latest head - The earlier blocker from my previous round was about the old runtime-status lookup path. On the current head, the test now gates on `container.getJobStatus(jobId)` through the SeaTunnel-side job-status path rather than the older Flink job-name matching path I was worried about before. - I do not see a reopened source-side blocker in the current revision of the exactly-once startup sequencing. - The current `Build` run is still pending, so the remaining gate is CI rather than a new code-side blocker from Daniel's side. So from the Daniel technical-review side, the latest head looks clear to me. If the current `Build` turns green, I would not have a new source blocker on top of this revision. -- 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]
