Add variable to allow users to exclude all results columns #382
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.
Overview
As can be seen in #369, there are issues where the BQ length gets too large. This has started happening since introducing this column to return all results available in the objects. Therefore, I have added a new variable
dbt_artifacts_exclude_all_results
which can be set totrue
to disable this column from being populated.Ideally, we'd want the default to be to 'not' include this field, but as it's been released with the field included (i.e. opt-in), it doesn't feel right to do that, so I have built it as an opt-out feature.
Update type - breaking / non-breaking
What does this solve?
Outstanding questions
What databases have you tested with?