Skip to content

Commit 44414ac

Browse files
authored
[DOCS] EQL: Document nested field support (#56138)
Notes that you cannot use EQL in ES to search the values of `nested` fields or their sub-fields. However, indices containing `nested` field mappings are otherwise supported.
1 parent a528319 commit 44414ac

File tree

2 files changed

+15
-1
lines changed

2 files changed

+15
-1
lines changed

docs/reference/eql/limitations.asciidoc

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,14 @@
88

99
experimental::[]
1010

11+
[discrete]
12+
[[eql-nested-fields]]
13+
=== EQL search on nested fields is not supported
14+
15+
You cannot use EQL to search the values of a <<nested,`nested`>> field or the
16+
sub-fields of a `nested` field. However, indices containing `nested` field
17+
mappings are otherwise supported.
18+
1119
[discrete]
1220
[[eql-unsupported-syntax]]
1321
=== Unsupported syntax

docs/reference/eql/requirements.asciidoc

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,6 @@ experimental::[]
1010

1111
EQL is schema-less and works well with most common log formats.
1212

13-
1413
[TIP]
1514
====
1615
While no schema is required to use EQL in {es}, we recommend the
@@ -34,3 +33,10 @@ A field containing the event classification, such as `process`, `file`, or
3433
Timestamp::
3534
A field containing the date and/or time the event occurred. This is typically
3635
mapped as a <<date,`date`>> field.
36+
37+
[NOTE]
38+
====
39+
You cannot use a <<nested,`nested`>> field datatype or the sub-fields of a
40+
`nested` field dataype as the timestamp or event category field. See
41+
<<eql-nested-fields>>.
42+
====

0 commit comments

Comments
 (0)