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_0/mappings.asciidoc

46 lines
1.7 KiB
Plaintext
Raw Normal View History

Remove the _all metadata field (#26356) * Remove the _all metadata field This change removes the `_all` metadata field. This field is deprecated in 6 and cannot be activated for indices created in 6 so it can be safely removed in the next major version (e.g. 7).
2017-08-28 11:43:59 -04:00
[[breaking_70_mappings_changes]]
=== Mapping changes
==== The `_all` meta field is removed
Reject the `index_options` parameter for numeric fields (#26668) Numeric fields no longer support the index_options parameter. This changes the parameter to be rejected in numeric field types after it was deprecated in 6.0. Closes #21475
2017-09-25 17:43:14 -04:00
The `_all` field deprecated in 6 have now been removed.
Remove legacy mapping code. (#29224) Some features have been deprecated since `6.0` like the `_parent` field or the ability to have multiple types per index. This allows to remove quite some code, which in-turn will hopefully make it easier to proceed with the removal of types.
2018-04-11 03:41:37 -04:00
==== The `_uid` meta field is removed
This field used to index a composite key formed of the `_type` and the `_id`.
Now that indices cannot have multiple types, this has been removed in favour
of `_id`.
Reject updates to the `_default_` mapping. (#29165) This will reject mapping updates to the `_default_` mapping with 7.x indices and still emit a deprecation warning with 6.x indices. Relates #15613 Supersedes #28248
2018-03-21 05:44:11 -04:00
==== The `_default_` mapping is no longer allowed
The `_default_` mapping has been deprecated in 6.0 and is now no longer allowed
in 7.0. Trying to configure a `_default_` mapping on 7.x indices will result in
an error.
Reject the `index_options` parameter for numeric fields (#26668) Numeric fields no longer support the index_options parameter. This changes the parameter to be rejected in numeric field types after it was deprecated in 6.0. Closes #21475
2017-09-25 17:43:14 -04:00
==== `index_options` for numeric fields has been removed
Limit the number of nested documents (#27405) Add an index level setting `index.mapping.nested_objects.limit` to control the number of nested json objects that can be in a single document across all fields. Defaults to 10000. Throw an error if the number of created nested documents exceed this limit during the parsing of a document. Closes #26962
2017-11-22 10:16:28 -05:00
The `index_options` field for numeric fields has been deprecated in 6 and has now been removed.
==== Limiting the number of `nested` json objects
To safeguard against out of memory errors, the number of nested json objects within a single
document across all fields has been limited to 10000. This default limit can be changed with
Remove the `update_all_types` option. (#28288) This option is not useful in 7.x since no indices may have more than one type anymore.
2018-01-22 06:03:07 -05:00
the index setting `index.mapping.nested_objects.limit`.
==== The `update_all_types` option has been removed
This option is useless now that all indices have at most one type.
Improve similarity integration. (#29187) This improves the way similarities are plugged in in order to: - reject the classic similarity on 7.x indices and emit a deprecation warning otherwise - reject unkwown parameters on 7.x indices and emit a deprecation warning otherwise Even though this breaks the plugin API, I'd like to backport to 7.x so that users can get deprecation warnings when they are doing something that will become unsupported in the future. Closes #23208 Closes #29035
2018-04-03 10:45:25 -04:00
[DOCS] Fixing formatting issues in breaking changes
2018-09-07 19:53:36 -04:00
==== The `classic` similarity has been removed
Improve similarity integration. (#29187) This improves the way similarities are plugged in in order to: - reject the classic similarity on 7.x indices and emit a deprecation warning otherwise - reject unkwown parameters on 7.x indices and emit a deprecation warning otherwise Even though this breaks the plugin API, I'd like to backport to 7.x so that users can get deprecation warnings when they are doing something that will become unsupported in the future. Closes #23208 Closes #29035
2018-04-03 10:45:25 -04:00
The `classic` similarity relied on coordination factors for scoring to be good
in presence of stopwords in the query. This feature has been removed from
Lucene, which means that the `classic` similarity now produces scores of lower
quality. It is advised to switch to `BM25` instead, which is widely accepted
as a better alternative.
[DOCS] Fixing formatting issues in breaking changes
2018-09-07 19:53:36 -04:00
==== Similarities fail when unsupported options are provided
Improve similarity integration. (#29187) This improves the way similarities are plugged in in order to: - reject the classic similarity on 7.x indices and emit a deprecation warning otherwise - reject unkwown parameters on 7.x indices and emit a deprecation warning otherwise Even though this breaks the plugin API, I'd like to backport to 7.x so that users can get deprecation warnings when they are doing something that will become unsupported in the future. Closes #23208 Closes #29035
2018-04-03 10:45:25 -04:00
An error will now be thrown when unknown configuration options are provided
to similarities. Such unknown parameters were ignored before.