[Microbatch] Leverage static partitioning in dbt-bigquery materialization strategy #802
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolves #538
docs dbt-labs/docs.getdbt.com/#
Problem
By using static partitions we are avoiding the extra steps of having to create tmp tables and then merging. Instead we use just one MERGE step.
Solution
Went through the jinja route to create the interval of partitions. Another option could have been using the generate the list of dates through
GENERATE_TIMESTAMP_ARRAY
(for 'hour' batch_size) orGENERATE_DATE_ARRAY
(for all others)Checklist