-
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
dbt Server errors when returning Array types in Postgres #2337
Milestone
Comments
drewbanin
added
bug
Something isn't working
redshift
rpc
Issues related to dbt's RPC server
labels
Apr 16, 2020
Update:
Thanks, Agate! |
drewbanin
added a commit
that referenced
this issue
Apr 17, 2020
drewbanin
added a commit
that referenced
this issue
May 2, 2020
iknox-fa
pushed a commit
that referenced
this issue
Feb 8, 2022
automatic commit by git-black, original commits: 0781cef
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
There's some sort of agate-internal issue with converting array type columns to an Agate dataframe from a Postgres response. TBD what the exact culprit is, but it manifests as
tuple.index(x): x not in tuple
called viaagate_table.table_from_data
(specifically intable.select(column_names)
). There's a solid reproduction case attached below.Steps To Reproduce
Run the query:
against a running rpc server. Poll for a response and see the error:
Expected behavior
I'd expect this query to return data successfully. The Array field should be json-ified, as with non-primitive types on other datbases (BQ, Snowflake).
System information
Which database are you using dbt with?
The output of
dbt --version
:The text was updated successfully, but these errors were encountered: