DanielLeens commented on issue #11558: URL: https://github.com/apache/seatunnel/issues/11558#issuecomment-5086321443
This is a valuable design topic, and it should stay on the STIP track rather than be treated like a normal feature issue. The strongest part of the proposal is that it makes the migration boundary explicit: `Lane A` is opt-in, `Lane B` keeps the legacy runtime, and restore never silently switches lane. That is the right starting point for something this iThe strongest part of the proposal is that it makes the migratitered on four questions: 1. whether the initial implementation can stay strictly limited to the Source runtime path, 2. how checkpoint metadata, capability digest, and attempt fencing prove restore compatibility, 3. whether Draft PR #11557 can be reviewed in phase-gated slices instead of as one monolithic change, 4. and what the minimum connector pilots plus conformance gates are before anything leaves Draft. If those boundaries stay firm, this is worth keeping open as a design-track STIP. -- 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]
