Schema handling while fabric mirroring is enabled on the Postgres destination
AnsweredWe are syncing data into a Postgres destination, and from this Postgres destination, we have mirroring enabled via Microsoft Fabric. Currently, whenever a schema change is made at the source side, it breaks the connection. This happens because the query fails at the destination, with an error stating that CDC is running in the destination.
Destination should throw a notification/task whenever a schema change is detected or if destination can handle automatically.
I have 70 connectors running with same source and destination types.
-
Hi Sobha,
Thanks for submitting this request—it’s very helpful feedback.
Improving notifications is a work in progress, and you should receive a notification when a schema evolution occurs.
To better understand the task-related part of your request: would you prefer the entire sync to stop when one or more tables encounter a schema evolution, or would you rather have those tables skipped while the sync continues for the remaining schemas and tables in the connection?
Best
Please sign in to leave a comment.
Comments
1 comment