DanielLeens commented on issue #11510: URL: https://github.com/apache/seatunnel/issues/11510#issuecomment-5040697519
Thanks for the very strong reproduction. I checked the packaging side, and this does look like a real image-level classpath conflict rather than a PostgreSQL setup problem. The current distribution assembly still pulls `org.opengauss:opengauss-jdbc` into the global `lib` set, while the normal PostgreSQL paths also rely on `org.postgresql.Driver`. Given that the openGauss driver keeps PostgreSQL package names, the failure mode you described is consistent with class resolution being hijacked before the Jdbc connector even gets a fair chance to use the intended pgJDBC implementation. PR #11522 is now open to remove that global-driver collision. This issue should stay open until the image-side fix lands and is validated again with a plain PostgreSQL container path like the one you documented. -- 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]
