Hi all! I've recently updated my dbt-bigquery to t...
# community-support
j
Hi all! I've recently updated my dbt-bigquery to the latest version and I've started experiencing similar problems to other people: Resources exceeded during query execution: Not enough resources for query planning - too many subqueries or query is too complex. I've searched and seen these threads: https://elementary-community.slack.com/archives/C02CTC89LAX/p1711672843688409 https://elementary-community.slack.com/archives/C02CTC89LAX/p1706780618622499 https://elementary-community.slack.com/archives/C02CTC89LAX/p1699452820286659 But I'm a little bit concerned of the impact that either of these changes:
Copy code
insert_rows_method: chunk
dbt_artifacts_chunk_size: 10000
Copy code
query_max_size: 100000
They might impact the other models running in the DBT run, is there a way that I can apply these variables only to the elementary models? Any help is greatly appreciated thanks!
✅ 1
Perfect thanks!
t
I will say there is currently a bug if you have both
insert_rows_method: chunk
and a
query_max_size
specified. It seemingly doesn't obey the query_max_size in that case.
j
Yeah I'm getting the exact same error - seems like ya raised this issue 2 months ago 😬
Have ya managed to find a workaround 🤔
t
I have not, sadly. There is PR from a contributor that addresses this, so I'm hoping our Elementary friends will take a look at it.
j
Ahh yeah this looks like this would fix the problem. Unfortunately I feel like we're going to have stop using elementary for the time being.
Thanks 😭
t
We are staying with an old version for now, but sadly that means our dbt tests metadata isn't populating correctly.
j
Did you stay with an older version of DBT or an older version of Elementary? I still want to stay on 1.7 of DBT. Does older versions of elementary work with 1.7?
p
[dbt-bigquery] I'm having this issue since I updated Elementary from 0.14.1 to 0.15.1
Copy code
Database Error in model dbt_columns (models/edr/dbt_artifacts/dbt_columns.sql)
Resources exceeded during query execution: Not enough resources for query planning - too many subqueries or query is too complex.
I've tried to include those variables on my dbt_project.yml, but still have the same problem
Copy code
insert_rows_method: chunk
dbt_artifacts_chunk_size: 10000
query_max_size: 100000
The only alternative is to downgrade? No fix to that yet?
b
I’m also encountering this issue on
elementary-data/elementary==0.15.2
p
Any news regrading this?
e
the PR mentioned here has been merged and this will be released in our next version 🙂
🙌 2
n
Hi @Ella Katz I’ve just bumped to the latest version of elementary (0.16.0) and still see this error, has the fix been released yet? & if so, what can I do to avoid the error?
b
Hello all, Im facing the same problem, although I've tried to include the variables mentioned above, the issue persists. I'd appreciate any help.
n
@Nick Gomez @Begüm Has I am also getting the same error. I wonder after upgrading to the latest version, did you run a full refresh? and did a rerun?
I am on 15.1 and if the upgrade is not helping, doesn't make any sense to update.
j
Hi all — I was also running into this “too many queries” issue after upgrading versions so I opened a GitHub issue about it here — https://github.com/elementary-data/elementary/issues/1689 feel free to comment if you have context you want to add. Hopefully we can get it resolved!
🙌 2
n
@jakem did you manage to solve this?
m
seems like the below is fixing the issue. insert_rows_method: chunk dbt_artifacts_chunk_size: 10000 query_max_size: 100000 However i dont understand how/where these variables are used in elementary and how did we come to know about these variable names?