[BUG] `dbt_expectations` `{{ DBT_EXPECTATIONS.TYPE_DATETIME() }}` not being rendered

[dbeatty10]

Describe the bug

    Failed target/generic_tests/dbt_expectations_expect_column_values_to_be_in_type_list_timeseries_data_date_datetime__date__dbt_expectations_type_datetime.sql

Here's the SQL that is executing and returning non-zero rows (zero rows indicates pass, otherwise fail).

Here's the row(s) indicating failure:

Root cause

Looks like the root cause is that there's some Jinja not being rendered prior to execution:

            relation_column_type not in ('DATE', '{{ DBT_EXPECTATIONS.TYPE_DATETIME() }}')

What version of dbt Fusion is this bug in? (find out by running dbt --version)

Is this a discrepancy between the dbt Fusion Engine and dbt Core? Check one.

• YES
• NO

To Reproduce

Instructions here.

cd integration_tests
dbt build --select test.dbt_expectations_integration_tests.dbt_expectations_expect_column_values_to_be_in_type_list_timeseries_data_date_datetime__date__dbt_expectations_type_datetime

Expected behavior

Pass without any errors.

Full log output

dbt-fusion 2.0.0-beta.24
   Loading profiles.yml
  Fetching packages.yml
   Loading dbt_project.yml
   Loading dbt_packages/dbt_date/dbt_project.yml
   Loading dbt_packages/dbt_expectations/dbt_project.yml
   Loading dbt_internal_packages/dbt-adapters/dbt_project.yml
   Loading dbt_internal_packages/dbt-snowflake/dbt_project.yml
warning: dbt1000: Detected nodes with unsafe introspection, skipping static analysis for these nodes and their downstreams. To enable unsafe static analysis, set static_analysis to 'unsafe' in the nodes configuration. Nodes: 'model.dbt_expectations_integration_tests.timeseries_base' (execute), 'model.dbt_expectations_integration_tests.timeseries_hourly' (execute)
 Rendering models/schema_tests/timeseries_base.sql
 Rendering models/schema_tests/timeseries_data.sql
   Running target/generic_tests/dbt_expectations_expect_column_values_to_be_in_type_list_timeseries_data_date_datetime__date__dbt_expectations_type_datetime.sql
    Failed target/generic_tests/dbt_expectations_expect_column_values_to_be_in_type_list_timeseries_data_date_datetime__date__dbt_expectations_type_datetime.sql
  Finished 'build' target 'snowflake' with 1 error and 1 warning in 2s 901ms 575us

Operating System and CPU Type (please complete the following information):

• Mac/Windows/Linux? N/A
• X86 or ARM? N/A

[MartinNeupauer]

When running a generic test on a column (defined in models/schema_tests/schema.yml):

    columns:
      - name: date_day
        tests:
          - dbt_expectations.expect_column_values_to_be_in_type_list:
              column_type_list: [date, "{{ dbt_expectations.type_timestamp() }}"]

the jinja is not rendered and the kwargs look like this column_type_list=["date","{{ dbt_expectations.type_datetime() }}"] and then the sql obviously chokes on that and hilarity ensues.

[venkaa28]

When running a generic test on a column (defined in models/schema_tests/schema.yml):

    columns:
      - name: date_day
        tests:
          - dbt_expectations.expect_column_values_to_be_in_type_list:
              column_type_list: [date, "{{ dbt_expectations.type_timestamp() }}"]

the jinja is not rendered and the kwargs look like this column_type_list=["date","{{ dbt_expectations.type_datetime() }}"] and then the sql obviously chokes on that and hilarity ensues.

If any kwarg has a jinja call we do some special processing here: https://github.com/dbt-labs/fs/blob/3e2f4537753e84482601dd94c6d34142aea484e8/fs/sa/crates/dbt-parser/src/resolve/resolve_tests/persist_generic_data_tests.rs#L1022

https://github.com/dbt-labs/fs/blob/3e2f4537753e84482601dd94c6d34142aea484e8/fs/sa/crates/dbt-parser/src/resolve/resolve_tests/persist_generic_data_tests.rs#L545

The kwarg should be rendered in a set statement and the kwarg passed into the actual macro should be a variable called:

dbt_custom_arg_<>

If this is failing it might be a bug in the jinja detection in a given kwarg.

[venkaa28]

Same issue as: #191