-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Docs snowflake 4 detailed migration guide #69728
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. Helpful Resources
PR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
|
|
|
||
| If you do not interact with the raw tables, you can safely upgrade. There is no breakage for this usecase. | ||
| :::note | ||
| Version 4 of the Snowfalke destination uses the `airbyte_internal` database for temporary scratch space (for example, streams running in dedup mode, truncate refreshes, and overwrite syncs). Dropping the entire `airbyte_internal database` can interrupt active syncs and cause data loss. Only drop the specific raw tables you no longer need. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'Snowfalke'?
|
|
||
| If you do not interact with the raw tables, you can safely upgrade. There is no breakage for this usecase. | ||
| :::note | ||
| Version 4 of the Snowfalke destination uses the `airbyte_internal` database for temporary scratch space (for example, streams running in dedup mode, truncate refreshes, and overwrite syncs). Dropping the entire `airbyte_internal database` can interrupt active syncs and cause data loss. Only drop the specific raw tables you no longer need. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'dedup'?
|
Deploy preview for airbyte-docs ready! ✅ Preview Built with commit 6cf894e. |
…69729) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: [email protected] <[email protected]>
| The number of underscores between `raw` and `stream` may vary depending on the longest underscore sequence in your namespace and stream names. | ||
|
|
||
| :::note | ||
| Version 4 of the Snowflake destination uses the `airbyte_internal` schema for temporary scratch space. For example, Airbyte needs this for streams running in dedup mode, truncate refreshes, and overwrite syncs. Dropping the entire `airbyte_internal` schema can interrupt active syncs and cause data loss. Only drop the specific raw tables you no longer need. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'dedup'?
What
This PR expands the Snowflake V4 migration guide. It includes more detailed instructions about how to handle legacy raw tables, particularly the use case where both raw and final tables are needed. It also provides more active clarification about how to clean up unnecessary raw tables after upgrade.
This is based on a customer request after they indicated they were not comfortable proceeding without more specific instructions.
How
Review guide
User Impact
Can this PR be safely reverted and rolled back?