From 85b52330c07c2d0107891b92a634dc362e9eb1aa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?= Date: Thu, 10 Oct 2024 18:16:43 +0200 Subject: [PATCH] [DOCS] Removes frozen indices limitation item from anomaly detection docs. (#2828) (cherry picked from commit 04632d2f1d1572bce948963a7ea10c99ab07ff7c) --- .../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 d9bd9ddd5..98aa76076 100644 --- a/docs/en/stack/ml/anomaly-detection/ml-limitations.asciidoc +++ b/docs/en/stack/ml/anomaly-detection/ml-limitations.asciidoc @@ -94,18 +94,6 @@ Analyzing large arrays results in long strings which may require more system 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-frozen-tier-limitations]] === {anomaly-jobs-cap} on frozen tier data cannot be created in {kib}