Use V2 templates when reading duplicate aliases and ingest pipelines#54902
Merged
dakrone merged 1 commit intoelastic:masterfrom Apr 8, 2020
Merged
Conversation
When a new index is rolled over, we check to see whether there are any duplicate alias configurations in the index template configuration. Additionally, when a new index is created from a bulk action, we check the templates to see if there are any ingest pipelines that need to be applied to the index that will be newly created. Both of these actions previously checked the v1 templates for their settings, they now also check the v2 index templates, with the v2 index templates taking precendence similar to the way they do when creating an index. Relates to elastic#53101
Collaborator
|
Pinging @elastic/es-core-features (:Core/Features/Indices APIs) |
Member
Author
|
This is subsequent work as Martijn pointed out in #54669 (comment) and #54669 (comment) |
Member
Author
|
@elasticmachine run elasticsearch-ci/bwc |
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this pull request
Apr 8, 2020
…tic#54902) When a new index is rolled over, we check to see whether there are any duplicate alias configurations in the index template configuration. Additionally, when a new index is created from a bulk action, we check the templates to see if there are any ingest pipelines that need to be applied to the index that will be newly created. Both of these actions previously checked the v1 templates for their settings, they now also check the v2 index templates, with the v2 index templates taking precendence similar to the way they do when creating an index. Relates to elastic#53101
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
When a new index is rolled over, we check to see whether there are any duplicate alias
configurations in the index template configuration. Additionally, when a new index is created from a
bulk action, we check the templates to see if there are any ingest pipelines that need to be applied
to the index that will be newly created.
Both of these actions previously checked the v1 templates for their settings, they now also check
the v2 index templates, with the v2 index templates taking precendence similar to the way they do
when creating an index.
Relates to #53101