@@ -48,7 +48,8 @@ image::images/esql/esql-lookup-join.png[align="center"]
4848lookup_index::
4949The name of the lookup index. This must
5050be 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]]
5455field_name::
@@ -142,6 +143,7 @@ any particular order. If a certain order is required, users should use a
142143
143144To 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
146148index 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
167169The 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
171173must be local.
172174* Currently, only matching on equality is supported.
0 commit comments