You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is necessarily a limitation with Debezium or this specific Debezium BigQuery connector. I successfully built and deployed a Docker image running debezium-server-bigquery. I was able to replicate all of our Postgres relational data into BigQuery tables in near real-time but I noticed that a large chunk of the table's columns' data types in BigQuery don't line up with those in our Postgres schemas. I found this documentation which explains the discrepancies I'm seeing. Basically all of the columns that are TIMESTAMP in Postgres are now STRING in BigQuery tables.
Is there any support built into the connector and/or Debezium for mapping the schema data types accordingly? What approaches have other folks used in this situation? It looks like it might be possible to write a custom table schema converter.
The text was updated successfully, but these errors were encountered:
I'm not sure if this is necessarily a limitation with Debezium or this specific Debezium BigQuery connector. I successfully built and deployed a Docker image running debezium-server-bigquery. I was able to replicate all of our Postgres relational data into BigQuery tables in near real-time but I noticed that a large chunk of the table's columns' data types in BigQuery don't line up with those in our Postgres schemas. I found this documentation which explains the discrepancies I'm seeing. Basically all of the columns that are
TIMESTAMP
in Postgres are nowSTRING
in BigQuery tables.Is there any support built into the connector and/or Debezium for mapping the schema data types accordingly? What approaches have other folks used in this situation? It looks like it might be possible to write a custom table schema converter.
The text was updated successfully, but these errors were encountered: