DanielLeens commented on issue #12267: URL: https://github.com/apache/seatunnel/issues/12267#issuecomment-5663649062
Thanks for the new complete log. This changes the diagnosis in a useful, but still pre-CDC, way. The initial `ClassNotFoundException` is no longer the terminal failure: the latest run reaches catalog connection with the standard `jdbc:postgresql://...` URL, 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. I also rechecked current `dev`: `PostgresIncrementalSourceFactory`, `PostgresIncrementalSource#driverName`, and `PostgresSourceConfigFactory` all use `org.postgresql.Driver`. Putting `HgdbJdbc-6.2.5.jar` beside a PostgreSQL JDBC jar therefore does not make this Postgres-CDC path use the HighGo driver, and mixing drivers is not a supported compatibility fix. Please next provide a sanitized, minimal compatibility matrix for the exact endpoint that fails: (1) the HighGo server authentication method / relevant `pg_hba.conf` rule and server version, (2) the exact PostgreSQL JDBC artifact version and the connector classloader-visible driver list, (3) a standalone connection using that same `jdbc:postgresql` URL and credentials, and then (4) a snapshot-only and a logical-replication run using the same database, schema, and table selection. Do not change replication ports or CDC configuration based on this authentication failure. If the server requires a HighGo-specific authentication protocol that the standard PostgreSQL driver cannot implement, please link the public protocol and compatible-license driver documentation. That would be a separately evidenced compatibility proposal, not a confirmed defect in the existing Postgres-CDC connector. -- 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]
