Adding mappings to data streams #129787
Open
Adding mappings to data streams #129787
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
masseyke
added
>non-issue
:Data Management/Data streams
|
Pinging @elastic/es-data-management (Team:Data Management) |
elasticsearchmachine
added
the
Team:Data Management
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.
This adds a mappings CompressedXContent object to each DataStream. This mappings object is serialized into the cluster state, and exposed via a getMappings(), getEffectiveMappings(), and getEffectiveIndexTemplate() methods . Right now it is not used by anything, but will be in subsequent PRs.
The code in this PR is not behind a feature flag, because there is no way for the code to have any user-facing impact, since there is no way yet to actually set a mapping on a data stream. The next PR will add the transport actions for getting and setting the mapping. The final PR will add the rest actions, API spec, and yaml rest tests. That will be behind a feature flag.