[Transform] Ignore IndexNotFound error when refreshing destination index #101627
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
|
Pinging @elastic/ml-core (Team:ML) |
|
Hi @przemekwitek, I've created a changelog YAML for you. |
💚 Backport successful
|
przemekwitek
added a commit
to przemekwitek/elasticsearch
that referenced
this pull request
Oct 31, 2023
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 31, 2023
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since introducing
unattendedmode for transforms, the destination index can be missing when transform is started.Because of this missing destination index, the
_refreshrequest on this index would fail withIndexNotFoundException.This PR fixes this by ignoring
IndexNotFoundExceptionwhen the destination index is missing as non-existent index does not need refreshing.