mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-07 05:28:34 +00:00
aa57bbd422
This improves modularity and also fixes some issues when `docvalues_fields` is used within `inner_hits` or the `top_hits` agg: * We previously didn't resolve wildcards in field names. * We also forgot to enforce the limit `index.max_docvalue_fields_search`.
33 lines
1009 B
Plaintext
33 lines
1009 B
Plaintext
[[breaking-changes-7.10]]
|
|
== Breaking changes in 7.10
|
|
++++
|
|
<titleabbrev>7.10</titleabbrev>
|
|
++++
|
|
|
|
This section discusses the changes that you need to be aware of when migrating
|
|
your application to {es} 7.10.
|
|
|
|
See also <<release-highlights>> and <<es-release-notes>>.
|
|
|
|
// * <<breaking_710_blah_changes>>
|
|
// * <<breaking_710_blah_changes>>
|
|
|
|
//NOTE: The notable-breaking-changes tagged regions are re-used in the
|
|
//Installation and Upgrade Guide
|
|
|
|
//tag::notable-breaking-changes[]
|
|
|
|
[discrete]
|
|
[[breaking_710_search_changes]]
|
|
=== Search Changes
|
|
|
|
[discrete]
|
|
==== Missing checks for `index.max_docvalue_fields_search`
|
|
The setting `index.max_docvalue_fields_search` limits the number of fields that
|
|
can be retrieved through `docvalue_fields` in a search. Previously we only
|
|
checked this limit when `docvalue_fields` appeared in the top-level search
|
|
request body. Now we also enforce the limit when loading doc value fields in
|
|
an `inner_hits` section or in a `top_hits` aggregation.
|
|
|
|
//end::notable-breaking-changes[]
|