Adding config option to set the timeout for the Elastic request #91
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.
Description
The purpose of this change is to add a new configuration option to set the timeout when performing an Elastic request.
I needed it on my Elastic cluster when performing search on large amount of data.
Motivation and Context
As explained in the description, the motivation of this change is to allow us to set the timeout for the Elastic request. The default timeout is quite low.
How Has This Been Tested?
It has been successfully tested on our test Resilient environment.
We also did non-regression testing : if you do not add this option in the configuration file, it is still working as before.
Checklist:
Signed-off-by: Stéphane Moreau smoreau@logikdev.com