Add BQ timeout to list of migration gotchas #6470
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are you changing in this pull request and why?
Customers migrating from v1.0 → v1.1+ may run into an issue with BigQuery timeouts. dbt Cloud has always set a default per-model timeout of 5 minutes (=
300
seconds), but in older versions of dbt (including v1.0) this config was inconsistently applied. The "fix" in v1.1+ means that customers will see timeouts on long-running models for the first time, even though this is the expected behavior.Context:
timeout_seconds
behaviour change compared to dbt 1.0 dbt-bigquery#201Add a note about BigQuery timeouts to the list of "gotchas" for customers being migrated from v1.0 to newer versions