DanielLeens commented on PR #11206:
URL: https://github.com/apache/seatunnel/pull/11206#issuecomment-7006931929

   Thanks @SEZ9. I agree that the safe quarantine lock boundary does not by 
itself close the configuration-aware JDBC capability check, retries while 
healthy queues are parked, single-initial-table path, DROP/re-CREATE handling, 
runtime admission bound or the documented skipped-row semantics. These are 
already part of Daniel's previous current-head conclusion; I am not adding 
duplicate numbered findings. Please address them together in the next commit 
and retain the failing restore-admission test as a separate concrete acceptance 
gate. The current dev conflict and exact-head CI remain independent 
requirements.


-- 
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]

Reply via email to