Make schema refresh timeout configurable via env var #7114
Merged
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.
What type of PR is this?
Description
In certain situations, especially when using managed (or "serverless") data services such as AWS Athena, it may take more than 300 seconds to refresh a single data source (pinging the API for all schemas from the cloud platform). We need longer timeout in these situations.
How is this tested?
Related Tickets & Documents
It solves #5402
Mobile & Desktop Screenshots/Recordings (if there are UI changes)