-
Notifications
You must be signed in to change notification settings - Fork 975
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
Clarify copy_partitions #4153
Clarify copy_partitions #4153
Conversation
Does not require ingestion time partitioning and is not a legacy mechanism
Hello!👋 Thanks for contributing to the dbt product documentation and opening this pull request! ✨ |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@mwstanleyft can you help me with a little more context here? the edit seems as if it's correcting a previously incorrect statement. is this specific to a version of dbt-bigquery or relevant to everyone? |
It's relevant to anyone on any version of dbt-bigquery. The old description called this a "legacy" mechanism but it's a fully supported feature of the BigQuery API. |
picking this up and asked in slack to confirm: https://dbt-labs.slack.com/archives/C067EUS2D7S/p1704896406558099 |
@mirnawong1 is attempting to deploy a commit to the dbt-labs Team on Vercel. A member of the Team first needs to authorize it. |
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.
hey @mwstanleyft thanks so much for your patience on this and apologies for the delay here. i appreciate you opening this up to clarify the docs and 've confirmed internally on our end. I will get this merged for you ✨
copy_partitions does not require ingestion time partitioning and is not a legacy mechanism
What are you changing in this pull request and why?
Clarifying when copy_partitions can be used and why it's useful.
Checklist