Anyone having issues in CI after upgrading to the latest version of DBT and Elementary.

430 of 878 OK created sql incremental model curve_ci_98830f92_elementary.dbt_columns  [CREATE TABLE (0.0 rows, 0 processed) in 2667.63s]

This model is now taking 45 minutes to run which seems slightly crazy..? Just curious what could be causing this now thanks?

dbt_columns

model was in Elementary 0.14, in 0.15 it was optimized to upload only documented columns (at least it's what I got analyzing source diff between versions). What is more interesting Elementary finds out if there are no changes in a project and then

dbt_columns

takes a couple of seconds. How big is your project? We have 200+ models and it takes 2-3 minutes to run all Elementary specific models with

dbt run -s package:elementary

. But what is more important is how much CPU and RAM you have on CI server. Elementary models are filled with post-hooks, which means all the calculations take place on client's side. So if you have limited CPU or/and MEM, it could take longer.

@Josh were you able to make any progress here? We’re experiencing similar issues, and I set

disable_dbt_columns_autoupload: true

, but we’re still getting ``Resources exceeded during query execution: Not enough resources for query planning - too many subqueries or query is too complex.` for our larger jobs (~500 models)

Hi, I am gettin gthis on older version as well. You got any solution?

I've just excluded the dbt_columns model in the dbt run for now. Seems to be the only way it works for me.