Combing dbtutils "surrogate key" with "get filtered columns in relation" produces new warning

joellabes · November 4, 2022, 5:23am

Sorry for the silence here! It feels like this is a bug, so an issue on utils would be the thing to do: Issues · dbt-labs/dbt-utils · GitHub

I am out of office for the next 2.5 weeks - if you wanted to do some exploration on your own, I would poke around in here, and see whether you could work out why it’s triggering unnecessarily:

github.com

dbt-labs/dbt-utils/blob/0.9.2/macros/sql/surrogate_key.sql#L10-L18


      
          {%- if varargs|length >= 1 or field_list is string %}
          
          
{%- set error_message = '
          Warning: the `surrogate_key` macro now takes a single list argument instead of \
          multiple string arguments. Support for multiple string arguments will be \
          deprecated in a future release of dbt-utils. The {}.{} model triggered this warning. \
          '.format(model.package_name, model.name) -%}
          
          
{%- do exceptions.warn(error_message) -%}

You could also try the utils 1.0 beta which replaces surrogate_key() with generate_surrogate_key() and doesn’t do this checking any more (if you give it a single string it’ll break).

Topic		Replies	Views
referring current model Help jinja , macros	1	1077	December 7, 2022
dbt_utils 0.8.6 surrogate_key Help surrogate-keys	1	1513	April 5, 2023
Error with generate_surrogate_key() Help surrogate-keys	2	2910	February 13, 2024
global variable Help	7	526	May 3, 2024
dbt_macro ( nvl ( column , dbt_macro (column)) Help jinja	0	1119	October 27, 2023

Combing dbtutils "surrogate key" with "get filtered columns in relation" produces new warning

Related topics