Error in Snowflake Destination Connector

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

Summary

The user is encountering an error in the Snowflake destination connector related to a COPY operation failure. They are unsure which logs to check for troubleshooting and how to identify the specific row/column causing the issue.


Question

Hitting this error line in snowflake destination connector: https://github.com/airbytehq/airbyte/blob/d34d7e627a50d38c73fb85e27905737b2bac1677/airbyte-integrations/connectors/destination-snowflake/src/main/kotlin/io/airbyte/integrations/destination/snowflake/operation/SnowflakeStagingClient.kt#L199|https://github.com/airbytehq/airbyte/blob/d34d7e627a50d38c73fb85e27905737b2bac1677[…]tions/destination/snowflake/operation/SnowflakeStagingClient.kt

java.lang.Exception: COPY into table failed with 1 errors, check logs

Does anyone know which logs are being referenced to check? Airbyte logs? Snowflake logs?
I am guessing it could be a result of some weird data but struggling to find how to identify the actual row/column info I need to troubleshoot. Suggestions welcome :slightly_smiling_face:


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

["error", "snowflake-destination-connector", "copy-operation", "troubleshooting", "logs"]
2

For issues with the Snowflake destination connector, I always start with the query monitoring logs in Snowflake

3

:cry: sadly I did check there and dont have any failed queries for the airbyte role

4

But under that role you do see other queries? So you know the role is being used?

5

I do :+1: lots of succeeded ones that show it was loading data. Just nothing that looks like it error’d out or didnt complete.

6

And your airbyte logs are set to info log level?

7

That is a good question. Do you know how I can confirm that?

8

I see lots of 2024-07-26 23:51:39 destination > INFO ... so maybe?

9

It’s an env var, but if you see info logs then it’s probably set to the default which is info. It is weird that there’s not a failed query

10

I agree, feels like it tried to run a copy command and failed in snowflake. Just cant find evidence of that in snowflake yet

11

I just have the same error, and you do not see it in the queries. you can see it in the stage load history. there is a view in information schema named load_history you can filter by status. In my case, the error was the size of the file. It was bigger than the default max size. I had to stop the ingestion of the table related to it, because I do not see a way to change that parameter yet