Make sure partition_by is in config if setting require_partition_filter #109
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 #107
Description
This PR adds an additional condition in
get_table_options
forrequire_partition_filter
. Essentially, both therequire_partition_filter
andpartition_by
options must both not be none forrequire_partition_filter
to work. This way, non-partitioned tables cannot haverequire_partition_filter
applied to them.This should allow users to just put
require_partition_filter
in the dbt_project.yml file instead of needing to make sure they only add it to configs for models that haspartition_by
in it.Checklist
CHANGELOG.md
and added information about my change to the "dbt-bigquery next" section.