forked from elastic/elasticsearch
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into handle-transform-reindex-failures
- Loading branch information
Showing
50 changed files
with
3,935 additions
and
980 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
pr: 117583 | ||
summary: Removing index alias creation for deprecated transforms notification index | ||
area: Machine Learning | ||
type: deprecation | ||
issues: [] | ||
deprecation: | ||
title: Removing index alias creation for deprecated transforms notification index | ||
area: Transform | ||
details: >- | ||
As part of the migration from 7.x to 8.x, the `.data-frame-notifications-1` index | ||
was deprecated and replaced with the `.transform-notifications-000002` index. | ||
The index is no longer created by default, all writes are directed to the new index, | ||
and any clusters with the deprecated index will have an alias created to ensure that | ||
reads are still retrieving data that was written to the index before the migration to 8.x. | ||
This change removes the alias from the deprecated index in 9.x. Any clusters with the alias present | ||
will retain it, but it will not be created on new clusters. | ||
impact: No known end user impact. |
Oops, something went wrong.