honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[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.
This commit is contained in:
Pius 2020-08-18 08:39:09 -07:00 committed by GitHub
parent d0c57c3068
commit d6ad247e07
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/reference/migration/migrate_7_0/search.asciidoc
View File

@ -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.
[discrete]
[[invalid-search-request-body]]