Closed rowanmoul closed 1 day ago
Thanks for reporting the issue @rowanmoul I added it to the connector backlog for further investigation in next sprints.
Please let me know if I can help dig into the problem further (eg, turning on more detailed logging, trying a debug version of the connector, etc). I should be able to reliably re-produce this issue on our dev server still.
@rowanmoul can you attach the full logs to this issue?
I'd rather not post them publicly, as it contains many of our table names. Can I send the log file to you on slack?
Thank you @rowanmoul for providing the logs on slack. What you posted in the description contains all the relevant information. We'll need to push a new version of the snowflake connector with a bit more logging, so we can see what query exactly is failing. The initial assessment is that the issue is probably caused by the high number of streams in your connection. If you want to get unblocked quickly, a workaround would be to split the connection into several connections with less than 50 streams each. I know it's not ideal though
Right now our workaround is running snowflake destination connector 3.5.14, which does not seem to have this problem with > 50 streams. When you have a new version with more logging let me know and I should be able to reproduce the issue just by upgrading the connector.
Will be solved by https://github.com/airbytehq/airbyte/pull/38585
Connector Name
destination-snowflake
Connector Version
3.6.0
What step the error happened?
During the sync
Relevant information
After updgrading the snowflake destination conntector to
3.7.0
, we started getting failed syncs saying we couldn't put more than 50 non-constant values in an "in-list", which I take to mean awhere x in (thing1, thing2)
clause. Walking back the versions, this appears to have started in version3.6.0
. Before the upgrade we were running3.5.14
without issue, and downgrading back to that version now allows syncs to finish without error, suggesting that something changed between3.5.14
and3.6.0
that causes the queries generated during sync to be invalid.One other interesting note is that when we reduce the number of tables that we are replicating from our postgresql source to 50 or less, the sync succeeds just fine on
3.6.0+
We are running the Airbyte Helm Chart version
0.64.205
at the moment, which lists the app version as0.57.3
Relevant log output
Contribute