Support include_type_name in the field mapping and index template APIs (backport to 6.x) #37319
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
jtibshirani
added
:Search Foundations/Mapping
Collaborator
|
Pinging @elastic/es-search |
jtibshirani
force-pushed
the
include-type-name
branch
3 times, most recently
from
2ed52e5 to
db59950
Compare
…s. (elastic#37210) * Add include_type_name to the get field mappings API. * Add include_type_name to the get index templates API. * Add include_type_name to the put index templates API.
jtibshirani
force-pushed
the
include-type-name
branch
from
db59950 to
bfdc33f
Compare
48 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Backport of #37210, opening to get a full build.
Note that this PR only introduces the REST parameter and does not add deprecation warnings, or make any changes to the HLRC.