[Bug] Fix scenario where dbt attempts to add existing columns to relations when using the SDK for column metadata #919
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 #914
Problem
When using the
redshift_connector
SDK to collect metadata about a relation,dbt-redshift
attempts to add a column to a model which already exists on the model. This does not occur when using the legacy metadata query.Solution
Still investigating, but it appears this could be related to case sensitivity and/or quoting. Changing a column from unquoted to quoted on an incremental model results in the error that the user reported. However, this error also occurs when using the legacy metadata query.
Checklist