DanielLeens commented on PR #11077: URL: https://github.com/apache/seatunnel/pull/11077#issuecomment-6514279166
Thanks @SEZ9. I agree that writer destination identity, aliased state ownership and schema/config compatibility remain correctness blockers on this unchanged head; the documented restore/implementer contracts remain part of the same source requests. Please address them together in a new commit and preserve existing coverage. GitHub also reports real merge conflicts: sync the latest base and resolve them while preserving both sides, then obtain a Build on the new head. Starting the existing fork workflow is a separate activation step; neither CI activation nor conflict resolution alone clears the source blockers. I am keeping this in the ordinary code/data-correctness review; no separate issue classification is inferred here. Checked 2026-10-30T03:30:37.153995+00:00; head `8b383c04eeed65c41a14ba756100a33f430124eb`. [Notify test workflow](https://github.com/apache/seatunnel/actions/runs/38302185787/job/114987521192)=`SUCCESS`; [labeler](https://github.com/apache/seatunnel/actions/runs/38302185861/job/114987522576)=`SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/114987916217)=`ACTION_REQUIRED`. Base `dev`, `diverged`, ahead 38/behind 171; merge `dirty`. This is an unchanged-head discussion/CI clarification, not another full source review or an effective approval. Daniel has READ repository permission. -- 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]
