This repository has been archived by the owner on Dec 22, 2023. It is now read-only.
Remove the ignore_conflicts option from the put mappings API #53
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
SanCoder-Q
force-pushed
the
remove-ic
branch
3 times, most recently
from
13e1b30 to
46a34c3
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Since ES 2.4, the
ignore_conflictsoption of the put mappings API isno longer supported according to
https://www.elastic.co/guide/en/elasticsearch/reference/2.4/breaking_20_mapping_changes.html
It will cause an
illegal_argument_exceptionerror with 400 HTTP codeif the client is used on the ES with the later version.
This PR is to remove the
ignore_conflictsoption.Related to the issue #51
PS. Fix the build.