-
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
run_sql command via dbt rpc returns Object of type Decimal is not JSON serializable #2336
Closed
1 of 5 tasks
Comments
drewbanin
changed the title
run_sql command via rbt rpc returns Object of type Decimal is not JSON serializable
run_sql command via dbt rpc returns Object of type Decimal is not JSON serializable
Apr 20, 2020
Thanks for the report @brettgriffin - this error occurs if a |
drewbanin
added a commit
that referenced
this issue
Apr 21, 2020
4 tasks
drewbanin
added a commit
that referenced
this issue
Apr 21, 2020
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Executing a
run_sql
command viadbt rbc
against a BigQuery profile returnsObject of type Decimal is not JSON serializable
. The equivalent command against Redshift, Snowflake, and PostgreSQL connections works correctly.Steps To Reproduce
A model exists with the body
with source as ( select * from {{source('recharge', 'orders')}} ) select * from source
.The query of the model is wrapped in a CTE limiting its results to 100 records:
And converted to base64:
A request is made to the RPC Server with the
run_sql
command, with the following body:Expected behavior
I would expect this to return the result set of the underlying sql statement.
Screenshots and log output
If applicable, add screenshots or log output to help explain your problem.
System information
Which database are you using dbt with?
The output of
dbt --version
:The operating system you're using: macOS 10.13.6
The output of
python --version
: 3.7Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: