DanielLeens commented on issue #11510: URL: https://github.com/apache/seatunnel/issues/11510#issuecomment-5148481162
Thanks for the follow-up root-cause analysis. The assembly boundary you pointed out is important. I agree this should be treated as a distribution / image classpath problem rather than as a PostgreSQL connectivity issue. The risky part is specifically putting `org.opengauss:opengauss-jdbc` into the same global runtime classpath as the regular PostgreSQL driver, because the openGauss driver keeps the `org.postgresql.Driver` package/class names. PR #11522 is still the linked fix path, but its current Build state is not green/complete, so this issue should remain open. The acceptance check after the fix should be simple and concrete: in the affected Docker image path, a standard PostgreSQL connection using `org.postgresql.Driver` must no longer be hijacked by the openGauss jar, while openGauss support remains available through the intended connector/plugin path. -- 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]
