Error importing new tables from Snowflake to Postgres

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

Airbyte detects new tables in Snowflake but encounters http.504 error when trying to replicate them to Postgres


Question

We have 16 connections with source “snowflake” and destination “postgres”.
The connections have been in production for months.
We added a new, empty table to each of the snowflake schemas.
The table is the same for every schema, with very simple column data types (2 timestamp, 12 varchar )
(again, the tables are empty, no data)

On every connection Airbyte detects the new tables, but when in Replication we try to add them we get this strange error, and the import fails: “Unknown error: http.504…….”

We have:
• Restarted airbyte
• Tried with data in the tables and empty
• Re-tested the source and destination access/auth
• we verified all other existing tables continue to sync ok
We are very confused — any hint appreciated.

We are just stuck and have no


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["snowflake", "postgres", "replication", "http-504-error", "table-sync", "airbyte"]
2

I noticed, that if your airbyte source, a table is empty, if with schema defined as in your case, such table will not be created in the destination.

Modified :

Use and click Refresh Source Schema button under Replication tab, you will see additional new tables from source. Ensure you save before resync again.

3

thank you <@U03UPS0983Z>!!

4

Good news is that we’re picking up source-snowflake and source-bigquery and we’ll rebuild them in python and take over supporting them.