[Bug]: Error when upgrading to 2.4.0 on BigQuery

[jdewet03]

Overview

We're unable to successfully rundbt run --select dbt_artifactswhen upgrading to 2.4.0

on-run-end failed, error:
The query is too large. The maximum standard SQL query length is 1024.00K characters, including comments and white space characters.

How to reproduce

On dbt solution using BigQuery:

• Implement and run dbt_artifacts version 2.3.0
• Upgrade dbt_artifacts version to 2.4.0
• Run: dbt run --select dbt_artifacts

We also tried deleting our dbt_artifacts schemas but same error

Expected behaviour

We expect to see the dbt command above complete succesfully

Screenshots

Environment

Results of running dbt --version:

1.4.6

Please paste the contents of your packages.yml file here:

packages:
  - package: dbt-labs/audit_helper
    version: [">=0.5.0", "<1.0.0"]

  - package: dbt-labs/dbt_utils
    version: [">=1.0.0", "<2.0.0"]
    
  - package: dbt-labs/codegen
    version: [">=0.5.0", "<1.0.0"]

  - package: data-mie/dbt_profiler
    version: [">=0.5.0", "<1.0.0"]

  - package: dbt-labs/dbt_project_evaluator
    version: [">=0.2.0", "<1.0.0"]

  - package: calogica/dbt_date
    version: [">=0.7.0", "<1.0.0"]

  - package: brooklyn-data/dbt_artifacts
    version: [">=2.3.0", "<3.0.0"]

[glsdown]

Hi @jdewet03 . Thanks for raising and sorry you are seeing this error. We are not able to replicate it locally, so I need to ask a few follow up questions to work out the cause. How large is your project? Specifically how many models do you have?

[jdewet03]

We have 175 models

[jdewet03]

Additional context and exact sequence of events:

• We were running successfully on 2.3.0 and once we upgraded to 2.4.0 this is the error we got

13:04:01  on-run-end failed, error:
13:04:01   Invalid input: Input number: 1685019801.1016695 cannot round-trip through string representation; error in PARSE_JSON expression

• I then ran dbt build --select package:dbt_artifacts manually on prod, without changing anything, to ensure it was not a once-off issue. This time it created a different error

13:08:30  on-run-end failed, error:
13:08:30   The query is too large. The maximum standard SQL query length is 1024.00K characters, including comments and white space characters.

• I then reverted to 2.3.0 and got yet another new error message

13:34:53  on-run-end failed, error:
13:34:53   Inserted row has wrong column count; Has 16, expected 17 at [9:9]

• I attempted to run a full refresh: dbt run -f -s dbt_artifacts but this did not change anything

13:39:08  on-run-end failed, error:
13:39:08   Inserted row has wrong column count; Has 16, expected 17 at [9:9]

• I deleted the dbt_artifact schemas entirely from our database and ran the package again with version 2.3.0 and it was successful

• Lasty, I deleted dbt_artifact schemas entirely from our database and ran the package again with version 2.4.0 and this was the error

13:43:52  on-run-end failed, error:
13:43:52   The query is too large. The maximum standard SQL query length is 1024.00K characters, including comments and white space characters.

[mbrummerstedt]

I have started to see the same issue

[jdewet03]

Issue resolved on our side thank you very much

[jared-rimmer]

Closing as should be fixed by 2.4.2. Feel free to open another issue if the issue persists.