SEZ9 commented on issue #11364: URL: https://github.com/apache/seatunnel/issues/11364#issuecomment-4976921593
Thanks for the detailed STIP. Could you also share the proposed API surface (REST endpoint shape and/or metrics naming) and how the model maps onto the existing job detail/metrics paths, so we can review backward compatibility? • Please add a per-connector capability matrix (required/optional/unsupported fields) for at least MySQL, PostgreSQL, Oracle, and TiDB CDC, and clarify lag semantics (time-based vs offset-based) where source timestamps are unavailable. • Suggest starting a DISCUSS thread on the dev mailing list to gather consensus on the model shape before implementation, and splitting the work into phases: core model, connector adapters, API exposure, then UI. -- 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]
