You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
query tagging is supported on models and snapshots in snowflake projects, but not on tests. Since tests also run queries against the warehouse, enabling tagging will allow users to have a fuller picture of dbt driven workloads.
Describe alternatives you've considered
pre / post hooks to set markers for test runs
reliance on user / environment naming conventions to separate workload data
github-actionsbot
changed the title
[Feature] enable query tagging for dbt tests on snowflake
[CT-796] [Feature] enable query tagging for dbt tests on snowflake
Jun 30, 2022
Hi,
My company is using DBT and planning to write data quality tests against Snowflake using dbt test. We have jobs that calculate the cost per query and attribute the cost appropriately. However, they have to be tagged. The tests are like any query and can run for very long so it is important to be able to tag and attribute the costs of test.
@matt-winkler Thanks for opening! The request feels totally reasonable, as does the implementation you've suggested: "wrapping" the default 'test' materialization, same as we do for seeds and snapshots.
github-actionsbot
changed the title
[CT-796] [Feature] enable query tagging for dbt tests on snowflake
[CT-893] [CT-796] [Feature] enable query tagging for dbt tests on snowflake
Jul 23, 2022
Is this your first time opening an issue?
Describe the Feature
query tagging is supported on
models
andsnapshots
in snowflake projects, but not ontests
. Since tests also run queries against the warehouse, enabling tagging will allow users to have a fuller picture of dbt driven workloads.Describe alternatives you've considered
Who will this benefit?
dbt + snowflake users
Are you interested in contributing this feature?
yes
Anything else?
here is how we manage this for snapshots.
The text was updated successfully, but these errors were encountered: