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
Currently, if you pass a string into a filter YAML param, it will be assumed to be a list. This means your semantic manifest ends up with a list of strings for where filters. For example, this YAML:
Is this a new bug in dbt-core?
Current Behavior
Currently, if you pass a string into a filter YAML param, it will be assumed to be a list. This means your semantic manifest ends up with a list of strings for where filters. For example, this YAML:
would look like this in the semantic manifest:
Expected Behavior
The semantic manifest should show this:
{"where_filters": [{"where_sql_template": "{{ Dimension('customer__customer_type') }} = 'new'"}]}
Steps To Reproduce
Add a string filter to a metric or saved query and run
dbt parse
, then look at the generated semantic manifest.Relevant log output
No response
Environment
Which database adapter are you using with dbt?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: