DanielLeens commented on PR #11382: URL: https://github.com/apache/seatunnel/pull/11382#issuecomment-6473935131
Thanks @SEZ9 for laying out the remaining concerns. My previous Not recommended for merge conclusion still stands on this unchanged head: in particular, the RestoreTableSchemaEvent interaction and the incorrect restore-mechanism Javadoc remain my numbered blockers. The green Build does not settle restore, completion-delivery or wire-contract questions. I am not adding duplicate numbered findings for your checklist or treating every newly asserted scenario as independently proved; the author should answer those paths with current-head evidence before we reconsider the merge conclusion. Gate snapshot (2026-10-28T15:59:34+00:00), head `e442d3db4791ebc289a842d76952557a3b5aa19d`: [Build](https://github.com/apache/seatunnel/runs/122199659411) is `SUCCESS`. The green check does not clear the independent source/documentation or scope requests in my [previous conclusion](https://github.com/apache/seatunnel/pull/11382#pullrequestreview-5676326930). Those requests remain unchanged; this is not an approval. Comparison recorded in this scan: base `dev`, `diverged`, ahead 9 / behind 16, no merge conflict. Branch drift is metadata here and is not an additional sync request. -- 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]
