Remove constant_keyword from the info API.#53071
Merged
jpountz merged 1 commit intoelastic:masterfrom Mar 4, 2020
Merged
Conversation
I discussed with @rjernst about what kind of functionality should be reported in the info API, since it doesn't sound sensible to list every single feature there. As a guideline, Ryan suggested that functionality that needs to maintain state should definitely be in the info API, but probably not field mappers like `constant_keyword`.
Collaborator
|
Pinging @elastic/es-search (:Search/Mapping) |
Contributor
Author
|
Thanks @rjernst ! |
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
4 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.
I discussed with @rjernst about what kind of functionality should be
reported in the info API, since it doesn't sound sensible to list every
single feature there. As a guideline, Ryan suggested that functionality
that needs to maintain state should definitely be in the info API, but
probably not field mappers like
constant_keyword.