From 546c69cf5aeec0f22fbd42ce9703c66a52a7a721 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 16 Apr 2025 12:20:23 +0200 Subject: [PATCH] [DOCS] [8.x] Update esql-lookup-join.md to mention index mode requirement Part of for #126897 8.x equivalent of https://github.com/elastic/elasticsearch/pull/126901/files --- docs/reference/esql/esql-lookup-join.asciidoc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/reference/esql/esql-lookup-join.asciidoc b/docs/reference/esql/esql-lookup-join.asciidoc index c78080258eb83..2dcf927d27dca 100644 --- a/docs/reference/esql/esql-lookup-join.asciidoc +++ b/docs/reference/esql/esql-lookup-join.asciidoc @@ -48,7 +48,8 @@ image::images/esql/esql-lookup-join.png[align="center"] lookup_index:: The name of the lookup index. This must be a specific index name - wildcards, aliases, and remote cluster -references are not supported. +references are not supported. Indices used for lookups must be configured with the <>. + [[esql-lookup-join-field-name]] field_name:: @@ -142,6 +143,7 @@ any particular order. If a certain order is required, users should use a To use `LOOKUP JOIN`, the following requirements must be met: +* Indices used for lookups must be configured with the <> * *Compatible data types*: The join key and join field in the lookup index must have compatible data types. This means: ** The data types must either be identical or be internally represented @@ -166,7 +168,7 @@ representations, see the <> mode are always single-sharded. +* Indices in <> mode are always single-sharded. * Cross cluster search is unsupported initially. Both source and lookup indices must be local. * Currently, only matching on equality is supported.