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
When your query takes too long to run, there is a timeout on Bigquery, and the query returns only the job_id.
In my own project (based in req_bigquery) I've replaced the first call, and always create a job (instead direct query), and then I call the job recursively to get the query results:
Yeah, I tried with timeout, but it still returned false, as documentation says
However, the call is not guaranteed to wait for the specified timeout; it typically returns after around 200 seconds (200,000 milliseconds), even if the query is not complete
When your query takes too long to run, there is a timeout on Bigquery, and the query returns only the job_id.
In my own project (based in req_bigquery) I've replaced the first call, and always create a job (instead direct query), and then I call the job recursively to get the query results:
I really don't know if something like that would work for req_bigquery / livebook
Best,
The text was updated successfully, but these errors were encountered: