-
Notifications
You must be signed in to change notification settings - Fork 131
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]: on-run-end
hook fails due to exceeding maximum standard SQL query length in BigQuery
#369
Comments
We are suffering from this too. DBT Cloud, Google BigQuery backend.
|
Hello. I've just put out a release in 2.6.0 which will hopefully help here. In a previous release, we added an additional In the latest release, I've added a variable that will stop this behaviour to reduce the query size. Please can you try adding the following as a variable in your dbt_artifacts_exclude_all_results: true |
This worked for us when pointing packages.yml at the main branch of dbt_artifacts. Will try 2.6.0. |
(update: problem resolved by waiting) |
I was too fast. It works now.
No 'query to large' errors anymore here (which we had in 2.4 and 2.5) |
That's great to hear! Thank you so much for confirming. I'm going to close this issue now, but if anything comes back again, please let me know and reopen this. |
Overview
For
dbt_artifact
versions2.4.0
,2.4.1
, and2.4.2
(anddbt-core
1.4.5
) theon-run-end
hook fails with the error:How to reproduce
Specify
dbt_artifacts
version2.4.0
,2.4.1
, or2.4.2
inpackages.yml
and run the commanddbt clean && dbt deps && dbt run --full-refresh --select dbt_artifacts
Expected behaviour
The command completes successfully. Note that
dbt_artifacts
version2.3.0
produces the expected behavior.Screenshots
Environment
Results of running
dbt --version
:Please paste the contents of your
packages.yml
file here:The text was updated successfully, but these errors were encountered: