feat(dbt): divest from fqn
in a subsetted execution
#21857
Merged
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.
Summary & Motivation
More thoughts on the line of #21851: we don't actually need
to rely on selecting by
fqn
, which can be very long.Instead, we can use other markers of uniqueness, if we assume that a project is standalone. This is a reasonable assumption, considering that multi-project setups are only supported by dbt Cloud.
From https://docs.getdbt.com/reference/node-selection/methods:
And https://docs.getdbt.com/faqs/models/unique-model-names:
So, for models and snapshots, we can rely on running tests by their file name.
And from: https://docs.getdbt.com/reference/node-selection/test-selection-examples#more-complex-selection
We can select tests using their test name.
After applying these optimizations when constructing the subset selection, the selection string is reduced in size by about 30-40%.
How I Tested These Changes
pytest