-
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
[Bug] tuple.index(x): x not in tuple #1626
Comments
drewbanin
added a commit
that referenced
this issue
Jul 30, 2019
This was referenced Jul 30, 2019
drewbanin
added a commit
that referenced
this issue
Jul 30, 2019
…rd-execute (#1626) fix for RPC error with BQ nested fields
fixed in #1638 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue
Issue description
On BigQuery, calls to
execute
withfetch=True
that return nested/repeated records fail with the errortuple.index(x): x not in tuple
. This happens because Agate coerces a nested field like{"col": [1,2,3]}
into a table likeWhen dbt tries to call
table.select(columns)
on the Agate table (in order to re-order the column as specified in the query, Agate raises an exception becauseselect(['col'])
is provided, but there is no such Column in the Agate table.This code path occurs primarily in calls to the
rpc
server.dbt version: >= 0.14.0
Possible Approaches:
select
The text was updated successfully, but these errors were encountered: