DanielLeens commented on issue #11047: URL: https://github.com/apache/seatunnel/issues/11047#issuecomment-4724984587
Thanks for picking this up and for already opening PR #11101. This is the right direction for the first delivery. The key thing now is to keep the initial scope tight and make the option propagation explicit rather than sink-specific ad hoc wiring. I've assigned the issue to @det101 so the current owner is visible from the issue state as well. For the first mergeable slice, please keep the review target focused on: 1. structured `table-options` propagation through the table abstraction 2. one JDBC end-to-end auto-create path as the primary proof point 3. clear fail-fast behavior for sinks that do not support the option path yet 4. focused tests plus both `docs/en` and `docs/zh` If a follow-up PR is needed for additional sinks, that is perfectly fine. It is better to land the JDBC-first slice cleanly than to widen the first patch too early. -- 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]
