DanielLeens commented on issue #10443: URL: https://github.com/apache/seatunnel/issues/10443#issuecomment-5602980315
Thanks for proposing a bounded Ingres slice. I checked current `dev`, the JDBC registration path, and the open PR set: there is no existing Ingres dialect or active Ingres PR. Please do not start a standalone Ingres source connector. First establish whether the existing generic JDBC source and sink can use the supported Ingres JDBC driver without adding a new bundled dependency, and post a short compatibility matrix covering driver coordinates and license, JDBC URL detection, quoting, type mapping, upsert behavior, and any actual divergence from the generic or PostgreSQL paths. A new driver dependency needs separate justification and packaging review. Once that evidence is posted, the intended first implementation can be a narrow `connector-jdbc` dialect/factory slice only for behavior that demonstrably differs. It must not expand into CDC, a separate connector module, catalog redesign, or speculative DDL behavior. If an official test image is available, propose one real JDBC integration path alongside focused dialect tests; otherwise state the concrete verification boundary before opening the PR. -- 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]
