Skip to content

Conversation

pmuellr
Copy link
Member

@pmuellr pmuellr commented Sep 2, 2025

Backport

This will backport the following commits from main to 9.1:

Questions ?

Please refer to the Backport tool documentation

…33846)

Part of elastic/kibana#231200 .

We realized that when the mappings are updated in a version upgrade,
the mappings are in fact updated, but not applied to the current
reporting datastream.

To fix this, we'll make a determination in Kibana that we should roll
over the data stream if the version in the template does not match the
version in the mappings of the datastream.  If they match, we don't need
to do anything.  If they don't match, or the version of the mappings is
not in the datastream (from before this PR), we will need to roll over the
data stream to apply the new mappings.

To make this happen, we need to add a new field to the mapping `_meta`,
which should match the template version.

references:

- https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/mapping-meta-field

Co-authored-by: Elastic Machine <[email protected]>
(cherry picked from commit ebb94bd)

# Conflicts:
#	x-pack/plugin/stack/src/main/java/org/elasticsearch/xpack/stack/StackTemplateRegistry.java
@pmuellr
Copy link
Member Author

pmuellr commented Sep 2, 2025

Note that REGISTRY_VERSION skipped 17, as the change for 17 was not backported this far back. See https://elastic.slack.com/archives/CE8P96STG/p1756832383465399 for more info.

@pmuellr pmuellr enabled auto-merge (squash) September 2, 2025 20:23
@pmuellr pmuellr merged commit 81f56dd into elastic:9.1 Sep 2, 2025
34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants