Skip to content

Commit ec0aa26

Browse files
ppf2jrodewig
authored andcommitted
[DOCS] Note max field expansions is not a hard limit (#61120)
Per #35284, it looks like we changed this from a max field expansions limit to a soft limit using the `indices.query.bool.max_clause_count` dynamic cluster settting.
1 parent f0ffdaf commit ec0aa26

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

docs/reference/migration/migrate_7_0/search.asciidoc

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -149,8 +149,11 @@ for a particular index with the index setting `index.max_regex_length`.
149149

150150
Executing queries that use automatic expansion of fields (e.g. `query_string`, `simple_query_string`
151151
or `multi_match`) can have performance issues for indices with a large numbers of fields.
152-
To safeguard against this, a hard limit of 1024 fields has been introduced for queries
153-
using the "all fields" mode ("default_field": "*") or other fieldname expansions (e.g. "foo*").
152+
To safeguard against this, a default limit of 1024 fields has been introduced for
153+
queries using the "all fields" mode (`"default_field": "*"`) or other fieldname
154+
expansions (e.g. `"foo*"`). If needed, you can change this limit using the
155+
<<indices-query-bool-max-clause-count,`indices.query.bool.max_clause_count`>>
156+
dynamic cluster setting.
154157

155158
[float]
156159
[[invalid-search-request-body]]

0 commit comments

Comments
 (0)