Support list of strings for incremental unique_key #19
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.
Description
In dbt 1.1 support was added for
unique_key
to be a list of strings as well as just a string. The dry runner fails to validate the manifest if a project uses this feature. This PR changes the pydantic model to allow list of strings forunique_key
. It also verifies that the snapshot model does not have a list ofunique_key
in case dbt adds this same feature to snapshot models and we need to update the node runner to handle this.Fixes #18
Checklist:
make verify
and fixed any linting or test errorsmake integration
against a Big Query instance