[Transform] Do not use PIT in the presence of remote indices in source #99803
Conversation
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
|
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
Sep 22, 2023
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 22, 2023
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.
Today transforms defaults to using point-in-time (PIT) readers. These can make the transform more efficient in many scenarios, however, there are some where they can make the transform considerably less efficient.
One of such scenarios is when some of the source indices are on remote clusters.
This PR disables PIT in such a case.
Relates #99742