SEZ9 commented on issue #12267: URL: https://github.com/apache/seatunnel/issues/12267#issuecomment-5673952742
Thanks for the complete log. With the latest run, the earlier `ClassNotFoundException` is no longer the terminal failure: the connector reaches the catalog connection using the `jdbc:postgresql://...` URL and then stops during JDBC authentication with `org.postgresql.util.PSQLException` reporting unsupported authentication type `13`. No snapshot reader, replication slot, publication, or WAL decoding has started at that point, so this is still a pre-CDC connectivity problem rather than a CDC defect. The Postgres-CDC connector uses `org.postgresql.Driver`, so placing `HgdbJdbc-6.2.5.jar` beside a PostgreSQL JDBC jar does not make this path use the HighGo driver, and mixing the two drivers is not a supported compatibility fix. To narrow this down, could you share (with credentials masked): the HighGo server version and the authentication method configured for this user, the exact PostgreSQL JDBC driver version on the classpath, and whether a standalone connection with the same `jdbc:postgresql` URL and credentials succeeds outside SeaTunnel? Please don't change replication ports or CDC settings based on this authentication failure. If the server requires a HighGo-specific authentication protocol that the standard PostgreSQL driver cannot implement, a link to public protocol and driver documentation would let us evaluate that as a separate compatibility proposal. <!-- streview-comment:1058 --> -- 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]
