Elasticsearch breaking changesedit

This list summarizes the most important breaking changes in Elasticsearch 8.1.3. For the complete list, go to Elasticsearch breaking changes.

REST API changesedit

The search API’s fields parameter now normalizes geometry objects that cross the international dateline

Details
The search API’s fields parameter now normalizes geo_shape objects that cross the international dateline (+/-180° longitude). For example, if a polygon crosses the dateline, the fields parameter returns it as two polygons. You can still retrieve original, unnormalized geometry objects from _source.

Impact
If your application requires unnormalized geometry objects, retrieve them from _source rather than using the fields parameter.

Cluster and node setting deprecationsedit

Legacy values for the discovery.type setting are deprecated

Details
Legacy values for the discovery.type setting are deprecated and will be forbidden in a future version.

Impact
Do not set discovery.type to any value except single-node or multi-node. All other values are equivalent to the default discovery type which is multi-node. Where possible, omit this setting so that Elasticsearch uses the default discovery type.

REST API deprecationsedit

Lenient parsing of bulk actions is deprecated

Details
Older versions of Elasticsearch parse the action lines of bulk requests very permissively and would silently ignore invalid or malformed actions. This lenience is deprecated and a future version will reject bulk requests containing invalid actions.

Impact
Ensure that bulk actions are well-formed JSON objects containing a single entry with the correct key.