Skip to content

Commit 9d6ef1f

Browse files
authored
[DOCS] [8.x] Update esql-lookup-join.md to mention index mode requirement (elastic#126905)
Part of for elastic#126897 8.x equivalent of https://github.com/elastic/elasticsearch/pull/126901/files
1 parent c9e7e5a commit 9d6ef1f

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

docs/reference/esql/esql-lookup-join.asciidoc

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,8 @@ image::images/esql/esql-lookup-join.png[align="center"]
4848
lookup_index::
4949
The name of the lookup index. This must
5050
be a specific index name - wildcards, aliases, and remote cluster
51-
references are not supported.
51+
references are not supported. Indices used for lookups must be configured with the <<index-mode-setting,`lookup` mode>>.
52+
5253

5354
[[esql-lookup-join-field-name]]
5455
field_name::
@@ -142,6 +143,7 @@ any particular order. If a certain order is required, users should use a
142143

143144
To use `LOOKUP JOIN`, the following requirements must be met:
144145

146+
* Indices used for lookups must be configured with the <<index-mode-setting,`lookup` mode>>
145147
* *Compatible data types*: The join key and join field in the lookup
146148
index must have compatible data types. This means:
147149
** The data types must either be identical or be internally represented
@@ -166,7 +168,7 @@ representations, see the <<esql-supported-types,Supported Field Types documentat
166168

167169
The following are the current limitations with `LOOKUP JOIN`
168170

169-
* Indices in <<index-mode-setting,lookup>> mode are always single-sharded.
171+
* Indices in <<index-mode-setting,`lookup`>> mode are always single-sharded.
170172
* Cross cluster search is unsupported initially. Both source and lookup indices
171173
must be local.
172174
* Currently, only matching on equality is supported.

0 commit comments

Comments
 (0)