[Transform] Allow transforms to use PIT with remote clusters again #105192
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
przemekwitek
force-pushed
the
revert_pit_restriction
branch
from
92d8756 to
57f1264
Compare
|
Hi @przemekwitek, I've created a changelog YAML for you. |
|
Pinging @elastic/ml-core (Team:ML) |
przemekwitek
added
>enhancement
and removed
Team:ML
|
Hi @przemekwitek, I've updated the changelog YAML for you. |
prwhelan
added a commit
to prwhelan/elasticsearch
that referenced
this pull request
Apr 26, 2024
…again (elastic#105192)" This reverts commit 9b584aa.
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.
There used to be problems with transforms using PIT together with remote source indices.
The mitigation was #99803.
Then the underlying issue got fixed so the mitigation can be reverted.
This PR does exactly this.
Closes #104518