-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[Transform] Ensure transform updates only modify the expected transform task #102934
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Pinging @elastic/ml-core (Team:ML) |
|
Hi @przemekwitek, I've created a changelog YAML for you. |
.../core/src/main/java/org/elasticsearch/xpack/core/transform/action/UpdateTransformAction.java
Show resolved
Hide resolved
|
As this is a very nasty bug I think the fix should be backported to the 8.11 and 7.17 branches. |
droberts195
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
💔 Backport failed
You can use sqren/backport to manually backport by running |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
…rm task (elastic#102934) (cherry picked from commit 67ab4b4) # Conflicts: # x-pack/plugin/core/src/test/java/org/elasticsearch/xpack/core/transform/action/UpdateTransformActionRequestTests.java
TransportUpdateTransformActionis aTransportTasksActionwhich means that it fans out to individual tasks running on the nodes.In order to find the appropriate tasks the
matchmethod must be implemented properly. For the_updateaction request thematchimplementation was missing which caused the action to fan out to all the transform persistent tasks causing unexpected changes in live (held in memory) transform settings.This PR implements the
matchmethod so that the problem is fixed.Closes #102933