This PR fixes a bug in our select_data_test_iasworld selector that I introduced in https://github.com/ccao-data/data-architecture/pull/638. The resource_type:test filter should be joined to the tag:data_test_iasworld filter using an intersection rather than a union. If we use a union instead, the selector will return all data tests instead of only data tests tagged with data_test_iasworld. I noticed this while debugging a failing workflow that was running the wrong number of tests. I mixed this up because union has a special meaning the case of the existing exclude filter, since that filter always returns a set difference.
I double-checked this change by inspecting the output of this query and confirming that the list of tests looked correct:
dbt list -q --selector select_data_test_iasworld
I also compared this to the non-YAML version of the selector to confirm they produce identical results:
dbt list -q --select tag:data_test_iasworld,resource_type:test --exclude tag:data_test_iasworld_exclude_from_workbook
This PR fixes a bug in our
select_data_test_iasworldselector that I introduced in https://github.com/ccao-data/data-architecture/pull/638. Theresource_type:testfilter should be joined to thetag:data_test_iasworldfilter using an intersection rather than a union. If we use a union instead, the selector will return all data tests instead of only data tests tagged withdata_test_iasworld. I noticed this while debugging a failing workflow that was running the wrong number of tests. I mixed this up becauseunionhas a special meaning the case of the existingexcludefilter, since that filter always returns a set difference.I double-checked this change by inspecting the output of this query and confirming that the list of tests looked correct:
I also compared this to the non-YAML version of the selector to confirm they produce identical results: