DanielLeens commented on issue #12267: URL: https://github.com/apache/seatunnel/issues/12267#issuecomment-5679935420
The new details narrow the boundary but do not yet establish a Postgres-CDC defect. The earlier missing-class failure is gone, and the standalone `jdbc:postgresql` connection succeeds; the connector still stops at PostgreSQL-driver authentication type 13 before snapshotting, slot creation, publication, or WAL decoding. The vendor JDBC guide you linked documents `com.highgo.jdbc.Driver` with a `jdbc:highgo:` URL, whereas SeaTunnel Postgres-CDC currently loads `org.postgresql.Driver` and uses the PostgreSQL/Debezium contract. Placing both jars on the classpath is therefore not a supported adapter. Please do not change replication ports or start a connector patch yet. To evaluate a separate compatibility proposal, provide the public protocol and driver-license documentation for SM3 plus a minimal, sanitized test matrix showing the exact driver and URL needed for snapshot and logical-replication access. A HighGo-specific driver path would need its own compatible-license dependency, real integration environment, and full snapshot/CDC validation; it is not a drop-in setting for the existing 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]
