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
Then, create a new model in that path (e.g., project_name/events/cool_events_facts.sql) and redefine sort-keys
{{
config(
sort=['day_of_week','version']
)
}}
When the model is built, the resulting SQL concatenates all four values, something like this (on Redshift):
create table
events.cool_events_facts
compound sortkey(day_of_week,version,occurred_at,client)
as (
select*from whatever
);
Expected behavior
My expectation is that the model-specific sort param overrides those in dbt_project, which is what happens when a string literal is used instead of a list.
Screenshots and log output
LMK if you need any more info!
System information
Which database are you using dbt with?
postgres
redshift
bigquery
snowflake
other (specify: ____________)
The output of dbt --version:
installed version: 0.15.0
latest version: 0.15.0
Up to date!
The operating system you're using:
macOS v10.14.6
The output of python --version:
Python 3.7.6
Additional context
Our current workaround is to define the model-specific sort params in dbt_project, which seems to override as expected.
The text was updated successfully, but these errors were encountered:
Describe the bug
We’ve run into an issue with defining sort config parameters in multiple places if both values are lists.
If…
then the resulting sort key is a concatenation of all of the keys, at least on Redshift (not sure how platform-dependent this might be).
Steps To Reproduce
Define a list of sort keys on a particular path in dbt_project
Then, create a new model in that path (e.g.,
project_name/events/cool_events_facts.sql
) and redefine sort-keysWhen the model is built, the resulting SQL concatenates all four values, something like this (on Redshift):
Expected behavior
My expectation is that the model-specific sort param overrides those in dbt_project, which is what happens when a string literal is used instead of a list.
Screenshots and log output
LMK if you need any more info!
System information
Which database are you using dbt with?
The output of
dbt --version
:The operating system you're using:
macOS v10.14.6
The output of
python --version
:Python 3.7.6
Additional context
Our current workaround is to define the model-specific sort params in dbt_project, which seems to override as expected.
The text was updated successfully, but these errors were encountered: