hello <@U04SE163WC8> Facing the following error w...
# replication-ask-ai
v
hello @kapa.ai Facing the following error when ingesting data from pgsql into clickhouse.
Copy code
:HTTPDriver for <https://uv5ogde86w.us-central1.gcp.clickhouse.cloud:8443> returned response code 404)
2023-10-18 03:44:37 normalization > 03:44:30.803478 [error] [MainThread]:    Code: 47. DB::Exception: Missing columns: '_airbyte_unique_key' while processing query
However, the column is already present on the table.
k
Hmm, I don't know enough to give you a confident answer yet. However, based on the information provided, it seems like there might be an issue with the data normalization process. The error message indicates that the '_airbyte_unique_key' column is missing while processing the query. You might want to check your source data in PostgreSQL and ensure that the '_airbyte_unique_key' column exists and is accessible. Also, ensure that the user you're using to connect to your ClickHouse destination has the necessary permissions to create tables and write rows [source](https://docs.airbyte.com/integrations/destinations/clickhouse). If you're still facing issues, I recommend checking out the [Airbyte troubleshooting guide](https://docs.airbyte.com/integrations/sources/postgres/postgres-troubleshooting) for more help.
A message from kapa.ai
Based on the information provided, it seems like there might be an issue with the data normalization process. The error message indicates that the '_airbyte_unique_key' column is missing while processing the query, even though you've confirmed that the column is present in the table. The '_airbyte_unique_key' is a hash of the primary key field, with some additional logic to handle records where this is undefined [source](https://airbyte.com/tutorials/incremental-data-synchronization). Here are a few things you could try: 1. Check the Data Types: Ensure that the data types of the '_airbyte_unique_key' column in your source (PostgreSQL) and destination (ClickHouse) are compatible. 2. Check the Permissions: Ensure that the user you're using to connect to your ClickHouse destination has the necessary permissions to read the '_airbyte_unique_key' column [source](https://docs.airbyte.com/integrations/destinations/clickhouse). 3. Recreate the Connection: As per a [forum post](https://discuss.airbyte.io/t/4483), a user facing a similar issue was able to resolve it by deleting the connection, dropping all Airbyte tables, and recreating the connection. If you're still facing issues, I recommend checking out the [Airbyte troubleshooting guide](https://docs.airbyte.com/integrations/sources/postgres/postgres-troubleshooting) for more help.