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

72 lines
2.4 KiB
Plaintext
Raw Normal View History

Remove sporadic min/max usage estimates from stats (#59755) Today `GET _nodes/stats/fs` includes `{least,most}_usage_estimate` fields for some nodes. These fields have rather strange semantics. They are only reported on the elected master and on nodes that have been the elected master since they were last restarted; when a node stops being the elected master these stats remain in place but we stop updating them so they may become arbitrarily stale. This means that these statistics are pretty meaningless and impossible to use correctly. Even if they were kept up to date they're never reported for data-only nodes anyway, despite the fact that data nodes are the ones where we care most about disk usage. The information needed to compute the path with the least/most available space is already provided in the rest the stats output, so we can treat the inclusion of these stats as a bug and fix it by simply removing them in this commit. Since these stats were always optional and mostly omitted (for opaque reasons) this is not considered a breaking change.
2020-07-20 09:48:53 -04:00
[[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[]
Consolidate validation for 'docvalue_fields'. (#60065) 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`.
2020-07-22 20:26:58 -04:00
[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.
Properly document keepalive and other tcp options (#60216) Keepalive options are not well-documented (only in transport section, although also available at http and network level). Co-authored-by: David Turner <david.turner@elastic.co> Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
2020-07-28 04:14:56 -04:00
[discrete]
[[breaking_710_networking_changes]]
=== Networking Changes
[discrete]
==== *.tcp.keep_idle and *.tcp.keep_interval now bounded
The settings `{network,transport,http}.tcp.keep_idle` and
`{network,transport,http}.tcp.keep_interval` are now limited to a maximum
value of 300, which amounts to 5 minutes. This helps ensure that, if
explicitly configured, only reasonable values are set.
Remove sporadic min/max usage estimates from stats (#59755) Today `GET _nodes/stats/fs` includes `{least,most}_usage_estimate` fields for some nodes. These fields have rather strange semantics. They are only reported on the elected master and on nodes that have been the elected master since they were last restarted; when a node stops being the elected master these stats remain in place but we stop updating them so they may become arbitrarily stale. This means that these statistics are pretty meaningless and impossible to use correctly. Even if they were kept up to date they're never reported for data-only nodes anyway, despite the fact that data nodes are the ones where we care most about disk usage. The information needed to compute the path with the least/most available space is already provided in the rest the stats output, so we can treat the inclusion of these stats as a bug and fix it by simply removing them in this commit. Since these stats were always optional and mostly omitted (for opaque reasons) this is not considered a breaking change.
2020-07-20 09:48:53 -04:00
//end::notable-breaking-changes[]
Deprecate Repository Stats API (#62297) (#62308) This commit deprecates the Repository Stats API added in 7.8.0 as an experimental API behind a feature flag. The goal is to deprecate this API in 7.10.0 and remove it in a follow up PR in 8.0.0. This API is now superseded by the Repositories Metering API.
2020-09-14 08:57:38 -04:00
.Repository Stats API is deprecated
[%collapsible]
====
*Details* +
The Repository Stats API has been introduced in 7.8.0 as an experimental API
and was never released. This API is superseded by the <<repositories-metering-apis,Repositories Metering APIs>>
added in 7.10.0 which should be used instead. The Repository Stats API is
deprecated starting 7.10.0 and will be removed in 8.0.0.
*Impact* +
Use the <<repositories-metering-apis,Repositories Metering APIs>>.
====
Emit deprecation warnings when boosts are defined in mappings (#62623) We removed index-time boosting back in 5x, and we no longer document the 'boost' parameter on any of our mapping types. However, it is still possible to define an index-time boost on a field mapper for a surprisingly large number of field types, and they even have an effect (sometimes, on some queries). As a first step in finally removing all traces of index time boosting, this comment emits a deprecation warning whenever a boost parameter is found on a mapping definition.
2020-09-18 10:34:54 -04:00
[[mapping-boosts]]
.The `boost` parameter on field mappings has been deprecated
[%collapsible]
====
*Details* +
Index-time boosts have been deprecated since the 5x line, but it is still possible
to declare field-specific boosts in the mappings. This is now deprecated as well,
and will be removed entirely in 8.0. Mappings containing field boosts will continue
to work in 7.x but will emit a deprecation warning.
*Impact* +
The `boost` setting should be removed from templates and mappings. Use boosts
directly on queries instead.
====