Snowflake Destination V2 still trying to utilize V1 raw tables #32479
Labels
area/connectors
Connector related issues
autoteam
community
team/destinations
Destinations team's backlog
Connector Name
destination-snowflake
Connector Version
3.4.10
What step the error happened?
During the sync
Relevant information
Suggested from here to create a new ticket.
When upgrading to Snowflake Destination > 3.x.x it is still trying to use the V1 raw tables over the V2 raw tables.
This error is "hidden" on upgrading from <3.x.x because those V1 raw tables still exists and most likely will lead to bad data since those V1 tables are no longer updated.
We came across this while testing other things and needed to create new connections, which will never complete due to this issue.
This can easily be reproduced by just creating a new connection pointing to a new schema/new prefix where the V1 raw tables would not exist for the table you are syncing.
We are stuck to Snowflake Destination
2.1.7
until this is resolvedc026278b_cd82_453e_a895_00935178025d_logs_2391_txt.txt
Relevant log output
Contribute
The text was updated successfully, but these errors were encountered: