DanielLeens commented on issue #10624:
URL: https://github.com/apache/seatunnel/issues/10624#issuecomment-4794941854

   Thanks for the follow-up.
   
   There are two separate issues mixed together here.
   
   First, `SelectDBCloud` is the cloud-specific sink path. For a SelectDB 
Enterprise deployment, the closer supported path is the `Doris` sink rather 
than `SelectDBCloud`, so the sink choice in the original config is already off.
   
   Second, the remaining PostgreSQL CDC failure is the duplicate 
replication-slot path. If you continue with Postgres CDC, please use a distinct 
`slot.name` explicitly instead of reusing the default slot name.
   
   This is also closely related to #10992, which tracks the duplicate-slot 
handling path more directly.
   
   For international community consistency, please use English when updating 
this issue.
   
   If you still reproduce the problem after:
   1. switching the sink to `Doris`
   2. setting a unique `slot.name`
   3. rechecking the current Postgres CDC behavior from #10992
   
   please update the thread with:
   - the exact Postgres server log around slot creation
   - the output of `select slot_name, database, plugin, active from 
pg_replication_slots;`
   - the revised SeaTunnel config


-- 
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]

Reply via email to