From 59c83abc8c880096c21cf1a28033300c24455bc9 Mon Sep 17 00:00:00 2001
From: Kofi B <kofi.bartlett@elastic.co>
Date: Tue, 21 Jan 2025 01:01:38 -0800
Subject: [PATCH] [DOCS] Update wildcard query documentation (#120251)

Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
---
 docs/reference/query-dsl/wildcard-query.asciidoc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/reference/query-dsl/wildcard-query.asciidoc b/docs/reference/query-dsl/wildcard-query.asciidoc
index 947b8d12f2a78..c2b4213a66866 100644
--- a/docs/reference/query-dsl/wildcard-query.asciidoc
+++ b/docs/reference/query-dsl/wildcard-query.asciidoc
@@ -81,6 +81,9 @@ the iterations needed to find matching terms and slow search performance.
 
 [[wildcard-query-notes]]
 ==== Notes
+
+Wildcard queries using `*` can be resource-intensive, particularly with leading wildcards. To improve performance, minimize their use and consider alternatives like the <<analysis-ngram-tokenizer,n-gram tokenizer>>. While this allows for more efficient searching, it may increase index size. For better performance and accuracy, combine wildcard queries with other query types like <<query-dsl-match-query,`match`>> or <<query-dsl-bool-query,`bool`>> to first narrow down results.
+
 ===== Allow expensive queries
 Wildcard queries will not be executed if <<query-dsl-allow-expensive-queries, `search.allow_expensive_queries`>>
 is set to false.