[Fleet] Update fleet mappings version #119087
Merged
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
nchaulet
added
auto-backport
|
@nchaulet please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
elasticsearchmachine
added
v9.0.0
external-contributor
juliaElastic
approved these changes
Dec 19, 2024
nchaulet
added
:Core/Infra/Core
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
💚 Backport successful
|
💔 Backport failedThe backport operation could not be completed due to the following error: You can use sqren/backport to manually backport by running |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Description
Resolve elastic/kibana#204834
Update mappings version for .fleet systems indices, we made a few change to .fleet indices without updating the mappings version. The consequence of this is the mappings are not updated on stack upgrade.
That PR fix that by increasing the mapping version for those indices.
How to tests?
I tested the upgrade from an 8.12 Elasticsearch to 8.18 than to that version with
And I was able to verify the .fleet indices have updated mappings, especially the
namespaces: keywordthat is required for Fleet space awareness