From b63a9e6dc6034e1904862b1d6900d59de2c8da03 Mon Sep 17 00:00:00 2001 From: Pius Date: Tue, 18 Aug 2020 08:39:09 -0700 Subject: [PATCH] [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. --- docs/reference/migration/migrate_7_0/search.asciidoc | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/reference/migration/migrate_7_0/search.asciidoc b/docs/reference/migration/migrate_7_0/search.asciidoc index b2cdfbd19cee3..3e2e85e29932a 100644 --- a/docs/reference/migration/migrate_7_0/search.asciidoc +++ b/docs/reference/migration/migrate_7_0/search.asciidoc @@ -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 +<> +dynamic cluster setting. [float] [[invalid-search-request-body]]