Skip to content

[8.18] ESQL: Add ENRICH vs LOOKUP JOIN to ENRICH docs (#125489) #125505

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 24, 2025
Merged

[8.18] ESQL: Add ENRICH vs LOOKUP JOIN to ENRICH docs (#125489) #125505

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/reference/esql/esql-enrich-data.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,15 @@ For example, you can use `ENRICH` to:
* Add product information to retail orders based on product IDs
* Supplement contact information based on an email address

<<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:

* Enrichment data doesn't change frequently
* You can accept index-time overhead
* You are working with structured enrichment patterns
* You can accept having multiple matches combined into multi-values
* You can accept being limited to predefined match fields
* `ENRICH` has a simplified security model. There are no restrictions to specific enrich policies or document and field level security.

[discrete]
[[esql-how-enrich-works]]
==== How the `ENRICH` command works
Expand Down