Hello all! I was SO CLOSE to not needing to ask f...
# replication-troubleshooting
t
Hello all! I was SO CLOSE to not needing to ask for help…so very close. I actually did get the synced data over but I have a major issue with it not ending up in the same schema - I’m going into Postgres, so it’s using the schema setup shown here -> https://docs.airbyte.com/integrations/destinations/postgres#schema-map, which of course, doesn’t work on the other end if you need the original schema. I’m really hoping there’s an easy fix :)
✍️ 1
u
@[DEPRECATED] Marcos Marx turned this message into Zendesk ticket 2822 to ensure timely resolution!
t
Extra information:
The end result is a database that runs a CMS - the sync is meant to pull data from mysql older versions of the site into a postgres new version
m
Today is not possible to have equal schema even if you’re using postgres to postgres. Airbyte will first convrt your record to the AirbyteMessage protocol and send to the destination, in this process your data can change. This is needed to achieve N-to-N connections, where you can connect any source to any destination.
t
Is there a way to map it?
Or is there a script available that would “unwrap it” essentially?
m
No, there isn’t 😞
You can… probably using dbt after running airbyte to re-map all your columns you need, or download the Airbyte normalization dbt module and edit it
But you have a lot of tables it can quite complicate to scale
t
Welp. That’s a dead end, then. Unfortunate.