-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Curious sortkey override behavior #2049
Milestone
Comments
drewbanin
added a commit
that referenced
this issue
Jan 20, 2020
drewbanin
added a commit
that referenced
this issue
Jan 20, 2020
Thanks for the report @ryanaustincarlson! I was able to reproduce this pretty easily, but it was tough getting to the bottom of the actual issue! I started working on a fix for this over here: #2062. This PR should be shipped for our next patch release, Edit: This will be going out in the 0.16.0 Barbara Gittings release |
drewbanin
added a commit
that referenced
this issue
Jan 20, 2020
drewbanin
added a commit
that referenced
this issue
Jan 24, 2020
Fixed by #2062 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: