[JAY-718] Add 'timeout' parameter to ClientFactory #46
Conversation
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
Adds the 'timeout' parameter to Elasticsearch::ClientFactory#create. The parameter allows the user to specify the number of seconds the underlying HTTP client will wait for Elasticsearch's response. The main driver behind this change is to alleviate some timeout errors that have been happening for complicated or large queries fetching big amounts of data.
sergio-bobillier
force-pushed
the
sb-JAY-718-add-timeout-parameters
branch
from
52ff7aa to
6f0fc78
Compare
sheputis
reviewed
Dec 10, 2025
sheputis
approved these changes
Dec 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds the
timeoutparameter toElasticsearch::ClientFactory#create. The parameter allows the user to specify the number of seconds the underlying HTTP client will wait for Elasticsearch's response.The main driver behind this change is to alleviate some timeout errors that have been happening for complicated or large queries fetching big amounts of data.