DanielLeens commented on issue #12267: URL: https://github.com/apache/seatunnel/issues/12267#issuecomment-5697152075
Thanks for testing the MD5 path. This is useful progress: it separates the HighGo-specific SM3 authentication incompatibility from the next source-initialization failure. It does not yet establish a database-name/schema-name confusion, because the exact replica-identity check and the selected-table metadata have not been shown. Please post the complete sanitized exception and the exact `database-names`, `schema-names`, `table-names`, and startup-mode settings used in the MD5 run. For the affected table, include the schema-qualified name and the relevant metadata (`pg_class.relreplident`, primary-key/unique-index definition, and any `ALTER TABLE ... REPLICA IDENTITY` setting). A primary key is normally compatible with the default replica identity, but we need the actual failing check to determine whether this is selection/configuration, table metadata, or a later HighGo logical-replication difference. After that, run one minimal snapshot-only job and one logical-replication job against the same single table with the standard PostgreSQL driver and the MD5 CDC user. Please keep ports and connector code unchanged for now. Those results will let us decide whether a normal Postgres-CDC configuration is supportable under that server/authentication combination or whether a separately designed HighGo compatibility proposal is needed. -- 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]
