Uh oh!
There was an error while loading. Please reload this page.
BigQuery: populate timeout parameter for getQueryResults - #4209
Conversation
This will allow QueryJob to respect the timeout value for futures.
| if self._done_timeout is not None: | ||
| # Subtract a buffer of a 100 milliseconds for context switching, | ||
| # network latency, etc. | ||
| timeout_ms = int(1000 * self._done_timeout) - 100 |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
| if self.state != _DONE_STATE: | ||
| self._query_results = self._client._get_query_results( | ||
| self.job_id, retry) | ||
| self.job_id, retry, |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
tswast
commented
Oct 18, 2017
Circle error is with Pub/Sub. cloud.google.bigquery tests are passing. Discussed timeout exception in person. The timeout option for getQueryResults is a parameter, not enforced client-side. When the time expires, the API will return a successful response with the incomplete job state. |
This will allow QueryJob to respect the timeout value for futures.
Closes#4135.