Skip to content
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: Overly verbose info-level logging for BigQuery queries that 404 #2383

Closed
drewbanin opened this issue Apr 30, 2020 · 0 comments · Fixed by #2393
Closed

Bug: Overly verbose info-level logging for BigQuery queries that 404 #2383

drewbanin opened this issue Apr 30, 2020 · 0 comments · Fixed by #2393
Labels
bigquery bug Something isn't working

Comments

@drewbanin
Copy link
Contributor

Describe the bug

I noticed this while reviewing #2378 -- when the catalog query failed with a 404 error, I saw the entire contents of the catalog query printed to stdout. Instead, the verbose BQ-generated error message should be logged to the debug logs.

Steps To Reproduce

This happens for both dbt run and dbt docs generate, and probably others too

  1. Set your location to US in your BQ profile
  2. Do a dbt run that creates at least one model in the db
  3. Change your location to northamerica-northeast1
  4. Run dbt run again and observe the stdout

Expected behavior

Stdout should not include the entire contents of the query that failed

The output of dbt --version:

dev/octavius-catto
@drewbanin drewbanin added bug Something isn't working bigquery labels Apr 30, 2020
@drewbanin drewbanin added this to the Octavius Catto milestone Apr 30, 2020
beckjake added a commit that referenced this issue May 4, 2020
…y-job-sql

Suppress the bigquery job sql in exception messages (#2383)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bigquery bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant