DanielLeens commented on issue #11402: URL: https://github.com/apache/seatunnel/issues/11402#issuecomment-5148480725
Thanks for splitting this into a contract PR and a runtime follow-up. That ordering makes sense for this issue. PR #11609 is the right first review surface because the main risk here is the SchemaChangeEvent runtime contract: per-table ordering, schema epoch boundaries, checkpoint interaction, replay after restore, sink apply semantics, and the unsupported-path behavior all need to be explicit before we spread the implementation across source, engine, and sink code. For PR #11614, the unsupported-sink fail-fast path is a reasonable implementation slice, but it should not be treated as closing the whole issue by itself. The larger checkpoint / replay / restore coordination work remains separate and should stay linked back to this thread after the contract PR is reviewed. So I would keep this issue open and use it as the umbrella for the contract plus follow-up implementation PRs. -- 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]
