mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 07:37:19 -04:00
e00b354c26
With https://github.com/elastic/stack-docs/pull/2495 merged, we no longer reuse breaking changes in the Stack Install/Upgrade guide. This removes the related `notable-breaking-changes[]` tags from the 8.9+ docs and updates the RN generator template. ## Out of scope With the removal of these tags, we may no longer need the `notable` property for changelog entries and can likely simplify the logic for the [BreakingChangesGenerator](https://github.com/elastic/elasticsearch/blob/main/build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/release/BreakingChangesGenerator.java). Updating those files is outside the scope of this PR. I've opened https://github.com/elastic/elasticsearch/issues/98145 to track that work.
133 lines
4.3 KiB
Text
133 lines
4.3 KiB
Text
[discrete]
|
|
[[breaking_80_mapping_changes]]
|
|
==== Mapping changes
|
|
|
|
.Indices created in {es} 6.x and earlier versions are not supported.
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
Elasticsearch 8.0 can read indices created in version 7.0 or above. An
|
|
Elasticsearch 8.0 node will not start in the presence of indices created in a
|
|
version of Elasticsearch before 7.0.
|
|
|
|
*Impact* +
|
|
Reindex indices created in {es} 6.x or before with {es} 7.x if they need to be carried forward to {es} 8.x.
|
|
====
|
|
|
|
.Closed indices created in {es} 6.x and earlier versions are not supported.
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
In earlier versions a node would start up even if it had data from indices
|
|
created in a version before the previous major version, as long as those
|
|
indices were closed. {es} now ensures that it is compatible with every index,
|
|
open or closed, at startup time.
|
|
|
|
*Impact* +
|
|
Reindex closed indices created in {es} 6.x or before with {es} 7.x if they need
|
|
to be carried forward to {es} 8.x.
|
|
====
|
|
|
|
.The maximum number of completion contexts per field is now 10.
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
The number of completion contexts within a single completion field
|
|
has been limited to 10.
|
|
|
|
*Impact* +
|
|
Use a maximum of 10 completion contexts in a completion field. Specifying more
|
|
than 10 completion contexts will return an error.
|
|
====
|
|
|
|
.Multi-fields within multi-fields is no longer supported.
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
Previously, it was possible to define a multi-field within a multi-field.
|
|
Defining chained multi-fields was deprecated in 7.3 and is now no longer
|
|
supported.
|
|
|
|
*Impact* +
|
|
To migrate mappings, all instances of `fields` that occur within
|
|
a `fields` block should be removed, either by flattening the chained `fields`
|
|
blocks into a single level, or by switching to `copy_to` if appropriate.
|
|
====
|
|
|
|
[[fieldnames-enabling]]
|
|
.The `_field_names` metadata field's `enabled` parameter has been removed.
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
The setting has been deprecated with 7.5 and is no longer supported on new indices.
|
|
Mappings for older indices will continue to work but emit a deprecation warning.
|
|
|
|
*Impact* +
|
|
The `enabled` setting for `_field_names` should be removed from templates and mappings.
|
|
Disabling _field_names is not necessary because it no longer carries a large index overhead.
|
|
====
|
|
|
|
[[mapping-boosts]]
|
|
.The `boost` parameter on field mappings has been removed.
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
Index-time boosts have been deprecated since the 5x line, but it was still possible
|
|
to declare field-specific boosts in the mappings. This is now removed completely.
|
|
Indexes built in 7x that contain mapping boosts will emit warnings, and the boosts
|
|
will have no effect in 8.0. New indexes will not permit boosts to be set in their
|
|
mappings at all.
|
|
|
|
*Impact* +
|
|
The `boost` setting should be removed from templates and mappings. Use boosts
|
|
directly on queries instead.
|
|
====
|
|
|
|
.Java-time date formats replace joda-time formats.
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
In 7.0, {es} switched from joda time to java time for date-related parsing,
|
|
formatting, and calculations. Indices created in 7.0 and later versions are
|
|
already required to use mappings with java-time date formats. However,
|
|
earlier indices using joda-time formats must be reindexed to use
|
|
mappings with java-time formats.
|
|
|
|
*Impact* +
|
|
For a detailed migration guide, see the {ref}/migrate-to-java-time.html[Java
|
|
time migration guide].
|
|
====
|
|
|
|
[[geo-shape-strategy]]
|
|
.Several `geo_shape` mapping parameters have been removed.
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
The following `geo_shape` mapping parameters were deprecated in 6.6:
|
|
|
|
* `tree`
|
|
* `tree_levels`
|
|
* `strategy`
|
|
* `distance_error_pct`
|
|
|
|
These parameters have been removed in 8.0.0.
|
|
|
|
*Impact* +
|
|
In 8.0, you can no longer create mappings that include these parameters.
|
|
However, 7.x indices that use these mapping parameters will continue to work.
|
|
====
|
|
|
|
.The `sparse_vector` field data type has been removed.
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
The `sparse_vector` field type was deprecated in 7.6 and is now removed in
|
|
8.0. We have not seen much interest in this experimental field type, and don't
|
|
see a clear use case as it's currently designed. If you have feedback or
|
|
suggestions around sparse vector functionality, please let us know through
|
|
GitHub or the 'discuss' forums.
|
|
|
|
*Impact* +
|
|
Discontinue use of the `sparse_vector` field data type. Requests containing
|
|
a mapping for this field data type will return an error.
|
|
====
|