[Transform] Allow dynamic updates to frequency#136757
Merged
prwhelan merged 4 commits intoelastic:mainfrom Oct 21, 2025
Merged
Conversation
Updates to a continuous transform's frequency should go into effect for the next transform's checkpoint without needed to stop and restart the transform. Fix elastic#133321
prwhelan
added
>bug
:ml/Transform
Collaborator
|
Hi @prwhelan, I've created a changelog YAML for you. |
Collaborator
|
Pinging @elastic/ml-core (Team:ML) |
jonathan-buttner
approved these changes
Oct 20, 2025
prwhelan
added a commit
to prwhelan/elasticsearch
that referenced
this pull request
Oct 21, 2025
Updates to a continuous transform's frequency should go into effect for the next transform's checkpoint without needed to stop and restart the transform. Fix elastic#133321
This was referenced Oct 21, 2025
prwhelan
added a commit
to prwhelan/elasticsearch
that referenced
this pull request
Oct 21, 2025
Updates to a continuous transform's frequency should go into effect for the next transform's checkpoint without needed to stop and restart the transform. Fix elastic#133321
Collaborator
prwhelan
added a commit
to prwhelan/elasticsearch
that referenced
this pull request
Oct 21, 2025
Updates to a continuous transform's frequency should go into effect for the next transform's checkpoint without needed to stop and restart the transform. Fix elastic#133321
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 21, 2025
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 21, 2025
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 21, 2025
chrisparrinello
pushed a commit
to chrisparrinello/elasticsearch
that referenced
this pull request
Oct 24, 2025
Updates to a continuous transform's frequency should go into effect for the next transform's checkpoint without needed to stop and restart the transform. Fix elastic#133321
fzowl
pushed a commit
to voyage-ai/elasticsearch
that referenced
this pull request
Nov 3, 2025
Updates to a continuous transform's frequency should go into effect for the next transform's checkpoint without needed to stop and restart the transform. Fix elastic#133321
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
4 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.
Updates to a continuous transform's frequency should go into effect for the next transform's checkpoint without needed to stop and restart the transform.
Fix #133321
Verified new integration test's stability with