Remove allow_type_wrapper setting
#9185
Merged
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
|
LGTM |
rjernst
force-pushed
the
remove/allow_type_wrapper
branch
from
4700db2
to
58bb9f5
Compare
Before Elasticsearch 1.0, the type was allowed to be passed as the root element when uploading a document. However, this was ambiguous if the mappings also contained a field with the same name as the type. The behavior was changed in 1.0 to not allow this, but a setting was added for backwards compatibility. This change removes the setting for 2.0.
rjernst
force-pushed
the
remove/allow_type_wrapper
branch
from
58bb9f5
to
060f963
Compare
rjernst
added
:Search/Mapping
clintongormley
changed the title
allow_type_wrapper setting
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.
Before Elasticsearch 1.0, the type was allowed to be passed as the root
element when uploading a document. However, this was ambiguous if the
mappings also contained a field with the same name as the type. The
behavior was changed in 1.0 to not allow this, but a setting was added
for backwards compatibility. This change removes the setting for 2.0.