Increase request timeout to avoid failed to add job: job already created errors#266
Merged
Merged
Conversation
Owner
|
Thank you for your contribution ! LGTM 👍 |
iolalla
pushed a commit
to iolalla/bigquery-emulator
that referenced
this pull request
Aug 16, 2025
Increase request timeout to avoid `failed to add job: job already created` errors
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In our use of the emulator we've encountered complex queries that take longer than 15 seconds to execute. The HTTP server's current configuration will close the connection after a 15 second timeout.
This causes the Python client to retry the request, using the same job id, resulting in the error as noted in #213
Closes #213