support for unique where clauses for each relation passed to union_relations #897
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: #895
This is a:
All pull requests from community contributors should target the
main
branch (default).Description & motivation
currently when a where clause is passed to union_relations, it is used for every relation that was passed. In some situations, this approach is not ideal. The proposed code change here maintains current functionality of passing strings to the where param but also allows for lists to be passed just like how the relations are passed to the relations parameter. Support for specific where clauses for each relation allows for more flexibility in the way the macro can be deployed
Checklist
star()
source)limit_zero()
macro in place of the literal string:limit 0
dbt.type_*
macros instead of explicit datatypes (e.g.dbt.type_timestamp()
instead ofTIMESTAMP