Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.14] Data Streams: Add ecs@mappings disclaimer for index templates cloned on ES < 8.13 (backport #1174) #1178

Merged
merged 1 commit into from
Jul 17, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Jul 17, 2024

Motivation

Starting from version 8.13, Elasticsearch includes the ecs@mappings component templates in all the index templates used in Elastic Agent integrations.

As integrations adopt the ecs@mappings component template, index templates cloned following the "Tutorial: Customize data retention policies" may start having problems with mappings.

End users must update their cloned index templates by adding the ecs@mappings component template.

Change description

This PR added a note and instructions to the tutorial users about updating the cloned index template they created following this tutorial.

Additional Notes

Reviewer checklist

  • PR address a single concern.
  • PR title and description are appropriately filled.
  • Changes will be merged in main.

This is an automatic backport of pull request #1174 done by [Mergify](https://mergify.com).

…on ES < 8.13 (#1174)

* Add disclaimer for index templates cloned < 8.13

* Suggest a roll over to apply the changes

* Minor edits

* Apple review suggestions

(cherry picked from commit 9ed0623)
@mergify mergify bot requested a review from a team as a code owner July 17, 2024 12:58
@mergify mergify bot added the backport label Jul 17, 2024
@mergify mergify bot assigned zmoog Jul 17, 2024
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@kilfoyle kilfoyle merged commit 7e5fbaf into 8.14 Jul 17, 2024
4 checks passed
@mergify mergify bot deleted the mergify/bp/8.14/pr-1174 branch July 17, 2024 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants