Add new Elasticsearch client as an alternative to the existing REST c… #2160
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
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.
This PR (almost) finishes integration of the new Elasticsearch client - although there are still some missing features and open issues which are addressed by separate issues.
Partly this is due to functionality missing from the new Elasticsearch client (#2139, #2150), or there was no time to finish this up before the 4.4 release (#2154, #2155, #2156).
I think it is important to have this state in the 4.4.0 release so that the integration of the new Elasticsearch can already be tested by users.
The missing features and updates from the Elasticsearch client will be implemented in both the main and 4.4.x branches as soon as possible.
Closes #1973