Changed Uri construction to consider empty typeName #124
Conversation
This file contains 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
According to Elastic (https://www.elastic.co/guide/en/elasticsearch/reference/current/removal-of-types.html) Elastic 7.x: Specifying types in requests is deprecated. For instance, indexing a document no longer requires a document type. Elastic 8.x: Specifying types in requests is no longer supported. (cherry picked from commit 378668cf3b930a071bc57967de2b88e8a5c661d7)
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.
According to Elastic (https://www.elastic.co/guide/en/elasticsearch/reference/current/removal-of-types.html)
Elastic 7.x: Specifying types in requests is deprecated. For instance, indexing a document no longer requires a document type.
Elastic 8.x: Specifying types in requests is no longer supported.
(cherry picked from commit 378668cf3b930a071bc57967de2b88e8a5c661d7)