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
I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
So the issue is coming directly from the - dbt_expectations.expect_column_values_to_be_of_type:. When testing with text, string ,or char values it returns 1 warning even though it should not.
Note:
When running the --store-failures command the first row returns that it has found a varchar value. This is the same whether the column_type is text string or char.
Expected Behavior
The example code i am using is :
- name: table_name
description: >
Table Description
columns:
- name: text_only_column
description: Column that only has text values
tests:
- dbt_expectations.expect_column_values_to_be_of_type:
column_type: text
config:
severity: warn
warn_if: "!=0"
- unique:
config:
severity: warn
warn_if: "!=0"
So i expect the run to not reproduce any errors since all of the values inside are handpicked to be text.
Steps To Reproduce
I have provided the code example along side the packages used in order to reproduce that error.
Is this a new bug in dbt-expectations?
Current Behavior
So the issue is coming directly from the
- dbt_expectations.expect_column_values_to_be_of_type:
. When testing with text, string ,or char values it returns 1 warning even though it should not.Note:
When running the --store-failures command the first row returns that it has found a varchar value. This is the same whether the column_type is text string or char.
Expected Behavior
The example code i am using is :
So i expect the run to not reproduce any errors since all of the values inside are handpicked to be text.
Steps To Reproduce
I have provided the code example along side the packages used in order to reproduce that error.
Environment
Which database adapter are you using with dbt?
I am using snowflake adapter
Additional Context
Packages used
The text was updated successfully, but these errors were encountered: