Skip to content

Commit

Permalink
[DOCS] Note max field expansions is not a hard limit (#61120)
Browse files Browse the repository at this point in the history
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.
  • Loading branch information
ppf2 authored and jrodewig committed Aug 18, 2020
1 parent d6ee39e commit b63a9e6
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions docs/reference/migration/migrate_7_0/search.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -149,8 +149,11 @@ for a particular index with the index setting `index.max_regex_length`.

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

[float]
[[invalid-search-request-body]]
Expand Down

0 comments on commit b63a9e6

Please sign in to comment.