From 445d0a9aa04b5174e087c9e76573d7e5d302ba2a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?= Date: Fri, 11 Oct 2024 13:13:36 +0200 Subject: [PATCH] [8.3][DOCS] Removes frozen indices limitation item from anomaly detection docs. (#2846) --- .../ml/anomaly-detection/ml-limitations.asciidoc | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/docs/en/stack/ml/anomaly-detection/ml-limitations.asciidoc b/docs/en/stack/ml/anomaly-detection/ml-limitations.asciidoc index 2c8eef758..9bd3b5e57 100644 --- a/docs/en/stack/ml/anomaly-detection/ml-limitations.asciidoc +++ b/docs/en/stack/ml/anomaly-detection/ml-limitations.asciidoc @@ -95,18 +95,6 @@ resources. Consider using a query in the {dfeed} that filters on the relevant items of the array. -[discrete] -[[ml-frozen-limitations]] -=== Frozen indices are not supported - -{ref}/frozen-indices.html[Frozen indices] cannot be used in {anomaly-jobs} or -{dfeeds}. This limitation applies irrespective of whether you create the jobs in -{kib} or by using APIs. This limitation exists because it's currently not -possible to specify the `ignore_throttled` query parameter for search requests -in {dfeeds} or jobs. See -{ref}/searching_a_frozen_index.html[Searching a frozen index]. - - [discrete] [[ml-forecast-config-limitations]] === Unsupported forecast configurations