From 2c69d1825b71cb60b0eb0e67577db125fda7a682 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?= Date: Thu, 19 Sep 2019 11:11:19 +0200 Subject: [PATCH] [DOCS][7.3] Adds data frame analytics field type and document limitation. --- .../df-analytics/dfanalytics-limitations.asciidoc | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/en/stack/ml/df-analytics/dfanalytics-limitations.asciidoc b/docs/en/stack/ml/df-analytics/dfanalytics-limitations.asciidoc index 452dc2132..0781414df 100644 --- a/docs/en/stack/ml/df-analytics/dfanalytics-limitations.asciidoc +++ b/docs/en/stack/ml/df-analytics/dfanalytics-limitations.asciidoc @@ -56,3 +56,16 @@ values will be skipped entirely. If there are missing values in feature fields (fields that are subjects of the {dfanalytics}), then the document that contains the fields with the missing values will be skipped during the analysis. + +[float] +[[dfa-od-field-type-docs-limitations]] +=== {oldetection-cap} field type and document limitation + +{oldetection-cap} requires numeric or boolean data to analyze. The algorithms +don't support missing values (see also <>), +therefore fields that have data types other than numeric or boolean are ignored. +Documents where included fields contain missing values, null values, or an array +are also ignored. Therefore a destination index may contain documents that don't +have an {olscore}. These documents are still reindexed from the source index to +the destination index, but they are not included in the {oldetection} analysis +and therefore no {olscore} is computed.