You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 7, 2026. It is now read-only.
Very excited by #1337, but ran into two main issues:
The types seem to be incorrect for client.query(query, options) (and client.query(query)). The types indicate the return type is [ResultsArray, IJob] (note in particular that job is not nested under a key "job" for the second value), whereas in practice I'm seeing a return shape of [ResultsArray, {job: IJob}, JobStatistics]. I'm unsure if the signature will change, so would like to make sure the types/return value is correct before using this
jobTimeoutMs cannot be set (only timeoutMs). Additionally, timeoutMs does not behave as expected. It seems like the request should max out at timeoutMs or some duration near that (perhaps RTT + timeoutMs). In reality, I'm observing it last for much longer if the job takes a while. It seems like the timeout is used for the initial jobsQuery request, then it is removed and the job continues to be awaited. This is critical to having some safety net for the maximum duration the fetch will take (jobTimeoutMs would be the preferred mechanism though).
Environment details
OS: n/a
Node.js version: n/a
npm version: n/a
@google-cloud/bigquery version: 7.8.0
Steps to reproduce
(Optionally) enable QUERY_PREVIEW_ENABLED env variable. I believe the issues reproduce without this too though
For the first bug,
Call client.query(jobOptions) (such as client.query({query: '<sql>'}))
Observe that three elements are returned instead of two, and the shape is incorrect
For the second bug,
Call client.query(jobOptions, { timeoutMs: 1000 }) with a job that would take >10s to execute.
Observe that the request hangs for >10s rather than aborting at 1s
Very excited to try out these preview features, but these are the issues blocking me from actually using it currently
Very excited by #1337, but ran into two main issues:
client.query(query, options)(andclient.query(query)). The types indicate the return type is[ResultsArray, IJob](note in particular that job is not nested under a key "job" for the second value), whereas in practice I'm seeing a return shape of[ResultsArray, {job: IJob}, JobStatistics]. I'm unsure if the signature will change, so would like to make sure the types/return value is correct before using thistimeoutMsor some duration near that (perhaps RTT + timeoutMs). In reality, I'm observing it last for much longer if the job takes a while. It seems like the timeout is used for the initial jobsQuery request, then it is removed and the job continues to be awaited. This is critical to having some safety net for the maximum duration the fetch will take (jobTimeoutMs would be the preferred mechanism though).Environment details
@google-cloud/bigqueryversion: 7.8.0Steps to reproduce
QUERY_PREVIEW_ENABLEDenv variable. I believe the issues reproduce without this too thoughFor the first bug,
client.query(jobOptions)(such asclient.query({query: '<sql>'}))For the second bug,
client.query(jobOptions, { timeoutMs: 1000 })with a job that would take >10s to execute.Very excited to try out these preview features, but these are the issues blocking me from actually using it currently