Skip to content

Commit 4956c26

Browse files
authored
ESQL: Add ENRICH vs LOOKUP JOIN to ENRICH docs (elastic#125489) (elastic#125505)
This was initially part of elastic#124531 but got lost during the manual backport.
1 parent fde490f commit 4956c26

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

docs/reference/esql/esql-enrich-data.asciidoc

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,15 @@ For example, you can use `ENRICH` to:
1515
* Add product information to retail orders based on product IDs
1616
* Supplement contact information based on an email address
1717

18+
<<esql-enrich>> is similar to <<esql-lookup-join,LOOKUP join>> in the fact that they both help you join data together. You should use `ENRICH` when:
19+
20+
* Enrichment data doesn't change frequently
21+
* You can accept index-time overhead
22+
* You are working with structured enrichment patterns
23+
* You can accept having multiple matches combined into multi-values
24+
* You can accept being limited to predefined match fields
25+
* `ENRICH` has a simplified security model. There are no restrictions to specific enrich policies or document and field level security.
26+
1827
[discrete]
1928
[[esql-how-enrich-works]]
2029
==== How the `ENRICH` command works

0 commit comments

Comments
 (0)