dbt-utils
dbt-utils copied to clipboard
dbt-labs
Utility functions for dbt projects.
Branched from https://github.com/dbt-labs/dbt-utils/pull/1007 resolves (partially) #1009 ### Problem > As part of our CI process, we use the `--empty` tag to run and test modified models with no data. However,...
Follow up from https://github.com/dbt-labs/dbt-core/issues/11274 ### Describe the feature Starting in dbt-core 1.10, we can validate our macro argument `name`s and `type`s: > Provide validation for macro arguments using the [validate_macro_args](https://docs.getdbt.com/reference/global-configs/behavior-changes#macro-argument-validation)...
### Describe the feature The [equality test](https://github.com/dbt-labs/dbt-utils/?tab=readme-ov-file#equality-source) supports passing a `compare_columns` setting, which allows one to limit the columns which will be compared from each relation. Critically, this setting assumes...
resolves #https://github.com/dbt-labs/dbt-utils/issues/1009 ### Problem As part of our CI process, we use the `--empty` tag to run and test modified models with no data. However, when these models use dbt_utils...
Compilation of models using `get_relations_by_pattern` macro fail if the macro returns [BigQuery `clone` type tables](https://cloud.google.com/bigquery/docs/table-clones-intro). ``` Runtime Error Field "type" of type Optional[RelationType] in BigQueryRelation has invalid value 'clone' ```...
treat CLONE type tables in BigQuery as 'table' resolves #955 ### Problem Compilation of models using `get_relations_by_pattern` macro fail if the macro returns [BigQuery `clone` type tables](https://cloud.google.com/bigquery/docs/table-clones-intro). ### Solution We...
### Describe the bug `mutually_exclusive_ranges.sql` does not work in Teradata. ### Steps to reproduce [`mutually_exclusive_ranges.sql`](https://github.com/dbt-labs/dbt-utils/blob/main/macros/generic_tests/mutually_exclusive_ranges.sql) does not work in Teradata. Please put the test in a yaml file and try...
### Describe the bug `generate_surrogate_key()` returns different results for redshift vs spark when a timestamp column includes trailing zeros in the milli-/micro-seconds ### Steps to reproduce Casting a timestamp to...
resolves #704 ### Problem In #704, it's expressed that it would be useful to limit the rows compared in the `equality` test. The issue was closed due to inactivity, but...
resolves #1000 ### Problem There is no way to compare two models using the `equality` test when the columns containing the same data have different column names. For example, if...