Microbatch: store model
context var as dict, not ModelNode
#10917
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: #10927
Resolves: dbt-labs/dbt-bigquery#1376
Problem
We were erroneously updating the
model
jinja context variable to be of typeModelNode
after re-compiling the microbatch model, when it should have been a dict. This was causing downstream issues in jinja when attempted to be accessed as a dict (e.g. not iterable, noget
method).Solution
model.to_dict()
MicrobatchBuilder
to centralize where context is being updated + ease of testing.Checklist