Skip to content

docs(config): clarify BigQuery timeoutMs semantics - #336

Open
girishjeswani wants to merge 3 commits into
malloydata:mainfrom
girishjeswani:docs/bigquery-timeoutms-semantics
Open

docs(config): clarify BigQuery timeoutMs semantics#336
girishjeswani wants to merge 3 commits into
malloydata:mainfrom
girishjeswani:docs/bigquery-timeoutms-semantics

Conversation

@girishjeswani

@girishjeswani girishjeswani commented Jul 29, 2026

Copy link
Copy Markdown

Companion to malloydata/malloy#3010, which changes what the BigQuery connection
timeoutMs bounds.

Before that PR, timeoutMs only bounded jobTimeoutMs; the results-fetch wait
was hard-capped near six minutes no matter what was configured. After it,
timeoutMs bounds the total wait (the BigQuery job and the results-fetch
polling), so the existing "Query timeout in ms" description is arguably only
becoming fully true now.

This updates the BigQuery timeoutMs row to spell out:

  • what it bounds now (the job plus results polling)
  • the default (600000, 10 min)
  • that an unset, blank, non-numeric, zero, or negative value falls back to that default

Per the cross-repo checklist in malloy at
packages/malloy/src/connection/CONTEXT.md.

…lling; 0 = no timeout)

Signed-off-by: Girish Jeswani <girish@credibledata.com>
Correct the BigQuery timeoutMs row: an unset, blank, non-numeric, or 0 value falls back to the 10-minute default, matching the connector change in malloydata/malloy#3010.

Signed-off-by: Girish Jeswani <girish@credibledata.com>
Signed-off-by: Girish Jeswani <girish@credibledata.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant