You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "DanielLeens (via GitHub)" <gi...@apache.org> on 2026/07/04 04:36:40 UTC
Re: [PR] Fix schema change routing for shared multi-table sinks [seatunnel]
DanielLeens commented on PR #11015:
URL: https://github.com/apache/seatunnel/pull/11015#issuecomment-4880664390
Thanks for the follow-up commits. I rechecked the latest head against the shared multi-table schema-change path again.
## Current state on the latest head
- I do not see a reopened source-side blocker in the shared physical-table schema-change routing path.
- The latest head still looks consistent on the core flow:
source schema change -> `MultiTableSinkWriter` dispatch/barrier -> per-writer drain -> shared physical sink schema refresh.
- The current `Build` run is still queued, 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 current revision still looks clear to me. Once the current `Build` settles green, this should be ready for the usual maintainer-side merge step.
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org