[Transform] Fix Missing Config Errors#134963
Merged
prwhelan merged 17 commits intoelastic:mainfrom Sep 24, 2025
Merged
Conversation
When there are more Transforms than the current page size, GET _transform will mistakenly display an error message `Found task for transform [...], but no configuration for it. To delete this transform use DELETE with force=true.`. When the page size is smaller than the reported total count of transforms, we will now get all Transform Ids and compare that to the running transforms to generate the dangling tasks error message. Resolve elastic#134263
prwhelan
added
>bug
:ml/Transform
Collaborator
|
Hi @prwhelan, I've created a changelog YAML for you. |
Collaborator
|
Pinging @elastic/ml-core (Team:ML) |
...gin/core/src/main/java/org/elasticsearch/xpack/core/transform/action/GetTransformAction.java
Outdated
Show resolved
Hide resolved
...gin/core/src/main/java/org/elasticsearch/xpack/core/transform/action/GetTransformAction.java
Outdated
Show resolved
Hide resolved
...form/src/main/java/org/elasticsearch/xpack/transform/action/TransportGetTransformAction.java
Show resolved
Hide resolved
Collaborator
💔 Backport failed
You can use sqren/backport to manually backport by running |
prwhelan
added a commit
to prwhelan/elasticsearch
that referenced
this pull request
Sep 24, 2025
This reverts commit 8a75ecd.
prwhelan
added a commit
to prwhelan/elasticsearch
that referenced
this pull request
Sep 24, 2025
When there are more Transforms than the current page size, GET _transform will mistakenly display an error message `Found task for transform [...], but no configuration for it. To delete this transform use DELETE with force=true.`. When the page size is smaller than the reported total count of transforms, we will now get all Transform Ids and compare that to the running transforms to generate the dangling tasks error message. Resolve elastic#134263
prwhelan
added a commit
to prwhelan/elasticsearch
that referenced
this pull request
Sep 24, 2025
When there are more Transforms than the current page size, GET _transform will mistakenly display an error message `Found task for transform [...], but no configuration for it. To delete this transform use DELETE with force=true.`. When the page size is smaller than the reported total count of transforms, we will now get all Transform Ids and compare that to the running transforms to generate the dangling tasks error message. Resolve elastic#134263
prwhelan
added a commit
to prwhelan/elasticsearch
that referenced
this pull request
Sep 24, 2025
When there are more Transforms than the current page size, GET _transform will mistakenly display an error message `Found task for transform [...], but no configuration for it. To delete this transform use DELETE with force=true.`. When the page size is smaller than the reported total count of transforms, we will now get all Transform Ids and compare that to the running transforms to generate the dangling tasks error message. Resolve elastic#134263
prwhelan
added a commit
to prwhelan/elasticsearch
that referenced
this pull request
Sep 24, 2025
When there are more Transforms than the current page size, GET _transform will mistakenly display an error message `Found task for transform [...], but no configuration for it. To delete this transform use DELETE with force=true.`. When the page size is smaller than the reported total count of transforms, we will now get all Transform Ids and compare that to the running transforms to generate the dangling tasks error message. Resolve elastic#134263
prwhelan
added a commit
to prwhelan/elasticsearch
that referenced
this pull request
Sep 24, 2025
When there are more Transforms than the current page size, GET _transform will mistakenly display an error message `Found task for transform [...], but no configuration for it. To delete this transform use DELETE with force=true.`. When the page size is smaller than the reported total count of transforms, we will now get all Transform Ids and compare that to the running transforms to generate the dangling tasks error message. Resolve elastic#134263
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 24, 2025
When there are more Transforms than the current page size, GET _transform will mistakenly display an error message `Found task for transform [...], but no configuration for it. To delete this transform use DELETE with force=true.`. When the page size is smaller than the reported total count of transforms, we will now get all Transform Ids and compare that to the running transforms to generate the dangling tasks error message. Resolve #134263
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 24, 2025
When there are more Transforms than the current page size, GET _transform will mistakenly display an error message `Found task for transform [...], but no configuration for it. To delete this transform use DELETE with force=true.`. When the page size is smaller than the reported total count of transforms, we will now get all Transform Ids and compare that to the running transforms to generate the dangling tasks error message. Resolve #134263
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 24, 2025
When there are more Transforms than the current page size, GET _transform will mistakenly display an error message `Found task for transform [...], but no configuration for it. To delete this transform use DELETE with force=true.`. When the page size is smaller than the reported total count of transforms, we will now get all Transform Ids and compare that to the running transforms to generate the dangling tasks error message. Resolve #134263
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 29, 2025
When there are more Transforms than the current page size, GET _transform will mistakenly display an error message `Found task for transform [...], but no configuration for it. To delete this transform use DELETE with force=true.`. When the page size is smaller than the reported total count of transforms, we will now get all Transform Ids and compare that to the running transforms to generate the dangling tasks error message. Resolve #134263
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.
When there are more Transforms than the current page size, GET _transform will mistakenly display an error message
Found task for transform [...], but no configuration for it. To delete this transform use DELETE with force=true..When the page size is smaller than the reported total count of transforms, we will now get all Transform Ids and compare that to the running transforms to generate the dangling tasks error message.
Resolve #134263
Also verified locally, without this change the UI will display this banner:
