PLUGIN-1800: Adding read timeout to BQ Execute Config with default 120s #1430
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.
https://cdap.atlassian.net/browse/PLUGIN-1800
Retries were already configured on the BigQuery Client by default, 5xx errors are being retried 6 times before failing:
Hence, increasing the read timeout for BigQuery Execute action plugin (where we are validating SQL) to a default of 120s. Earlier timeout was the BigQuery default of 20s.
Confirmed via local sandbox testing that the default timeout for BigQuery Execute is 120s.