You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a transform has no config document but still has a task it becomes invisible, both GET and _stats do not list the them. This situation can happen if the documents got deleted manually or the whole transform internal index got deleted. System indices will prevent this to some extent, however it would be nice to handle such a corner case.
It is possible to force delete or stop an invisible transform, but you need to know they exist and you need the name.
We should improve the above and list invisible transforms in GET and _stats (if not in both, at least in 1 of them.)
Requirements:
ensure a invisible transform is listed after creation of the transform and deletion of its config (hint: we have an integration test for this for delete/stop)
the invisible transform should not be listed next to good ones, but somehow marked as broken (HLRC lists "invalid_transforms", maybe something similar)
ensure interaction in the transform UI keeps working, it should be possible to delete the transform, but not start/update it (might require kibana changes, create issue once we have a design)
Hint:
TransformNodes.findPersistentTasks as used for _stop
The text was updated successfully, but these errors were encountered:
We should improve the above and list invisible transforms in GET and _stats (if not in both, at least in 1 of them.)
It's done for GET but not for _stats.
The example response from GET when there exists a transform task without config is:
{
"count" : 0,
"transforms" : [ ],
"errors" : [
{
"type" : "dangling_task",
"reason" : "Found task for transform [cont-t-1], but no configuration for it. To delete this transform use DELETE with force=true."
}
]
}
If a transform has no config document but still has a task it becomes invisible, both
GET
and_stats
do not list the them. This situation can happen if the documents got deleted manually or the whole transform internal index got deleted. System indices will prevent this to some extent, however it would be nice to handle such a corner case.It is possible to
force
delete or stop an invisible transform, but you need to know they exist and you need the name.We should improve the above and list invisible transforms in
GET
and_stats
(if not in both, at least in 1 of them.)Requirements:
Hint:
TransformNodes.findPersistentTasks
as used for_stop
The text was updated successfully, but these errors were encountered: