Skip to content

Commit d58636e

Browse files
committed
[DOCS] Adds nested objects related inference limitation (#791)
1 parent 7957480 commit d58636e

File tree

1 file changed

+15
-4
lines changed

1 file changed

+15
-4
lines changed

docs/en/stack/ml/df-analytics/dfanalytics-limitations.asciidoc

Lines changed: 15 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,18 @@ that don't contain a results field are not included in the {reganalysis}.
9898
=== {classification-cap} field types
9999

100100
{classification-cap} supports fields that have numeric, boolean, text, keyword,
101-
or ip data types. It is also tolerant of missing values. Fields that are supported are
102-
included in the analysis, other fields are ignored. Documents where included
103-
fields contain an array are also ignored. Documents in the destination index
104-
that don't contain a results field are not included in the {classanalysis}.
101+
or ip data types. It is also tolerant of missing values. Fields that are
102+
supported are included in the analysis, other fields are ignored. Documents
103+
where included fields contain an array are also ignored. Documents in the
104+
destination index that don't contain a results field are not included in the
105+
{classanalysis}.
106+
107+
[float]
108+
[[dfa-inference-nested-limitation]]
109+
=== Deeply nested objects affect {infer} performance
110+
111+
If the data that you run inference against contains documents that have a series
112+
of combinations of dot delimited and nested fields (for example:
113+
`{"a.b": "c", "a": {"b": "c"},...}`), the performance of the operation might be
114+
slightly slower. Consider using as simple mapping as possible for the best
115+
performance profile.

0 commit comments

Comments
 (0)