root
/
elasticsearch
mirror of https://github.com/elastic/elasticsearch.git
1
0
Fork 0
Code Issues Actions 1 Packages Projects Releases Wiki Activity
elasticsearch/docs/reference/migration/migrate_8_0.asciidoc

92 lines
3.0 KiB
Plaintext
Raw Normal View History

[DOCS] Adds placeholders for v8 highlights, breaking changes, release notes (#38641)
2019-02-09 07:48:42 +08:00
[[breaking-changes-8.0]]
== Breaking changes in 8.0
++++
<titleabbrev>8.0</titleabbrev>
++++
This section discusses the changes that you need to be aware of when migrating
your application to {es} 8.0.
See also <<release-highlights>> and <<es-release-notes>>.
Remove `nGram` and `edgeNGram` token filter names (#38911) In #30209 we deprecated the camel case `nGram` filter name in favour of `ngram` and did the same for `edgeNGram` and `edge_ngram`. Using these names has been deprecated since 6.4 and is issuing deprecation warnings since then. I think we can remove these filters in 8.0. In a backport of this PR I would change what was a dreprecation warning from 6.4. to an error starting with new indices created in 7.0.
2019-02-16 03:15:05 +08:00
coming[8.0.0]
Percentiles aggregation: disallow specifying same percentile v… (#52257) Disallow specifying the same percentile multiple times in percentiles aggregation Related: #51871
2020-02-26 20:40:33 +08:00
* <<breaking_80_aggregations_changes>>
Always auto-release the flood-stage block (#45274) Removes support for using a system property to disable the automatic release of the write block applied when a node exceeds the flood-stage watermark. Relates #42559
2019-08-08 18:47:14 +08:00
* <<breaking_80_allocation_changes>>
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
* <<breaking_80_analysis_changes>>
Fixed synchronizing REST API inflight breaker names with internal variable (#40878) The internal configuration settings were like that: network.breaker.inflight_requests But the exposed REST API had the value names with underscore like that: network.breaker.in_flight_requests This was now corrected to without underscores like that: network.breaker.inflight_requests
2019-09-03 20:56:36 +08:00
* <<breaking_80_breaker_changes>>
Remove node filters for voting config exclusions (#55673) The use of node filters for excluding nodes from the voting configuration was deprecated in #50836; this commit removes support for node filters in this API. Closes #47990
2020-04-24 23:04:47 +08:00
* <<breaking_80_cluster_changes>>
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
* <<breaking_80_discovery_changes>>
* <<breaking_80_http_changes>>
Add ILM poll_interval limit to breaking changes (#41095) ILM's poll_interval setting now has a lower limit of 1 second, which is technically a breaking change.
2019-04-13 00:43:10 +08:00
* <<breaking_80_ilm_changes>>
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
* <<breaking_80_indices_changes>>
Make Fuzziness reject illegal values earlier (#33511) The current java implementation of Fuzziness leaves a lot of room for initializing it with illegal values that either cause errors later when the queries reach the shards where they are executed or values that are silently ignored in favour of defaults. We should instead tighten the java implementation of the class so that we only accept supported values. Currently those are numeric values representing the edit distances 0, 1 and 2, optionally also as float or string, and the "AUTO" fuzziness, which can come in a cusomizable variant that allows specifying two value that define the positions in a term where the AUTO option increases the allowed edit distance. This change removes several redundant ways of object construction and adds input validation to the remaining ones. Java users should either use one of the predefined constants or use the static factory methods `fromEdits(int)` or `fromString(String)` to create instances of the class, while other ctors are hidden. This allows for instance control, e.g. returning one of the constants when creating instances from an integer value. Previously the class would accept any positive integer value and any float value, while in effect the maximum allowed edit distance was capped at 2 in practice. These values while throw an error now, as will any other String value other than "AUTO" that where previously accepted but led to numeric exceptions when the query was executed.
2019-04-05 16:35:35 +08:00
* <<breaking_80_java_changes>>
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
* <<breaking_80_mappings_changes>>
Remove deprecated transport settings (#40918) This is related to #36652. There are a number of transport settings that were deprecated and replaced with new versions in 7.x. This commit removes them from 8.0.
2019-04-13 05:42:05 +08:00
* <<breaking_80_network_changes>>
Remove node.max_local_storage_nodes (#42428) This setting, which prior to Elasticsearch 5 was enabled by default and caused all kinds of confusion, has since been disabled by default and is not recommended for production use. The preferred way going forward is for users to explicitly specify separate data folders for each started node to ensure that each node is consistently assigned to the same data path. Relates to #42426
2019-05-23 22:02:12 +08:00
* <<breaking_80_node_changes>>
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
* <<breaking_80_packaging_changes>>
Reindex from Remote encoding (#41007) Removed the leniency when encoding remote reindex search requests that was introduced in 7.x. All index-names are now encoded before being sent to the remote host. Follow-up to #40303
2019-04-16 22:46:54 +08:00
* <<breaking_80_reindex_changes>>
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
* <<breaking_80_api_changes>>
* <<breaking_80_rollup_changes>>
Remove CommonTermsQuery and cutoff_frequency param (#42654) Remove `common` query and `cutoff_frequency` parameter of `match` and `multi_match` queries. Both have already been deprecated for the next 7.x version. Closes: #37096
2019-05-31 23:06:06 +08:00
* <<breaking_80_search_changes>>
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
* <<breaking_80_security_changes>>
Remove deprecated search.remote settings (#42381) We deprecated these settings awhile ago, in favor of cluster.remote. In 7.x we were gentle and provided automatic upgrade of these settings to the new settings. Now it is time for them to go. This commit removes the deprecated search.remote settings.
2019-05-23 23:06:07 +08:00
* <<breaking_80_settings_changes>>
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
* <<breaking_80_snapshots_changes>>
* <<breaking_80_threadpool_changes>>
* <<breaking_80_transport_changes>>
Remove `nGram` and `edgeNGram` token filter names (#38911) In #30209 we deprecated the camel case `nGram` filter name in favour of `ngram` and did the same for `edgeNGram` and `edge_ngram`. Using these names has been deprecated since 6.4 and is issuing deprecation warnings since then. I think we can remove these filters in 8.0. In a backport of this PR I would change what was a dreprecation warning from 6.4. to an error starting with new indices created in 7.0.
2019-02-16 03:15:05 +08:00
[DOCS] Removes notable breaking changes section
2019-03-23 06:45:13 +08:00
//NOTE: The notable-breaking-changes tagged regions are re-used in the
//Installation and Upgrade Guide
[DOCS] Adds notable changes section (#38238)
2019-03-09 02:51:27 +08:00
//tag::notable-breaking-changes[]
[float]
==== Indices created before 7.0
Enforce Completion Context Limit (#38675) This change adds a limit to the number of completion contexts that a completion field can define. Closes #32741
2019-02-18 19:51:40 +08:00
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.
[IMPORTANT]
.Reindex indices from Elasticsearch 6.x or before
=========================================
Indices created in Elasticsearch 6.x or before will need to be reindexed with
Elasticsearch 7.x in order to be readable by Elasticsearch 8.x.
=========================================
Remove deprecated endpoints containing _xpack. (#48170) The endpoints with `_xpack` in their path were deprecated in 7.x and can now be removed. This commit removes deprecated endpoints for the following APIs: * deprecation * graph * license * monitoring * rollup * SQL * watcher
2019-10-29 09:23:04 +08:00
[float]
==== REST endpoints containing `_xpack`
In 7.0, we deprecated REST endpoints that contain `_xpack` in their path. These
endpoints are now removed in 8.0. Each endpoint that was deprecated and removed
is replaced with a new endpoint that does not contain `_xpack`. As an example,
`/{index}/_xpack/graph/_explore` is replaced by `/{index}/_graph/explore`.
[DOCS] Adds notable changes section (#38238)
2019-03-09 02:51:27 +08:00
// end::notable-breaking-changes[]
Enforce Completion Context Limit (#38675) This change adds a limit to the number of completion contexts that a completion field can define. Closes #32741
2019-02-18 19:51:40 +08:00
Percentiles aggregation: disallow specifying same percentile v… (#52257) Disallow specifying the same percentile multiple times in percentiles aggregation Related: #51871
2020-02-26 20:40:33 +08:00
include::migrate_8_0/aggregations.asciidoc[]
Always auto-release the flood-stage block (#45274) Removes support for using a system property to disable the automatic release of the write block applied when a node exceeds the flood-stage watermark. Relates #42559
2019-08-08 18:47:14 +08:00
include::migrate_8_0/allocation.asciidoc[]
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
include::migrate_8_0/analysis.asciidoc[]
Fixed synchronizing REST API inflight breaker names with internal variable (#40878) The internal configuration settings were like that: network.breaker.inflight_requests But the exposed REST API had the value names with underscore like that: network.breaker.in_flight_requests This was now corrected to without underscores like that: network.breaker.inflight_requests
2019-09-03 20:56:36 +08:00
include::migrate_8_0/breaker.asciidoc[]
Remove node filters for voting config exclusions (#55673) The use of node filters for excluding nodes from the voting configuration was deprecated in #50836; this commit removes support for node filters in this API. Closes #47990
2020-04-24 23:04:47 +08:00
include::migrate_8_0/cluster.asciidoc[]
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
include::migrate_8_0/discovery.asciidoc[]
include::migrate_8_0/http.asciidoc[]
Add ILM poll_interval limit to breaking changes (#41095) ILM's poll_interval setting now has a lower limit of 1 second, which is technically a breaking change.
2019-04-13 00:43:10 +08:00
include::migrate_8_0/ilm.asciidoc[]
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
include::migrate_8_0/indices.asciidoc[]
Make Fuzziness reject illegal values earlier (#33511) The current java implementation of Fuzziness leaves a lot of room for initializing it with illegal values that either cause errors later when the queries reach the shards where they are executed or values that are silently ignored in favour of defaults. We should instead tighten the java implementation of the class so that we only accept supported values. Currently those are numeric values representing the edit distances 0, 1 and 2, optionally also as float or string, and the "AUTO" fuzziness, which can come in a cusomizable variant that allows specifying two value that define the positions in a term where the AUTO option increases the allowed edit distance. This change removes several redundant ways of object construction and adds input validation to the remaining ones. Java users should either use one of the predefined constants or use the static factory methods `fromEdits(int)` or `fromString(String)` to create instances of the class, while other ctors are hidden. This allows for instance control, e.g. returning one of the constants when creating instances from an integer value. Previously the class would accept any positive integer value and any float value, while in effect the maximum allowed edit distance was capped at 2 in practice. These values while throw an error now, as will any other String value other than "AUTO" that where previously accepted but led to numeric exceptions when the query was executed.
2019-04-05 16:35:35 +08:00
include::migrate_8_0/java.asciidoc[]
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
include::migrate_8_0/mappings.asciidoc[]
Remove deprecated transport settings (#40918) This is related to #36652. There are a number of transport settings that were deprecated and replaced with new versions in 7.x. This commit removes them from 8.0.
2019-04-13 05:42:05 +08:00
include::migrate_8_0/network.asciidoc[]
Remove node.max_local_storage_nodes (#42428) This setting, which prior to Elasticsearch 5 was enabled by default and caused all kinds of confusion, has since been disabled by default and is not recommended for production use. The preferred way going forward is for users to explicitly specify separate data folders for each started node to ensure that each node is consistently assigned to the same data path. Relates to #42426
2019-05-23 22:02:12 +08:00
include::migrate_8_0/node.asciidoc[]
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
include::migrate_8_0/packaging.asciidoc[]
Reindex from Remote encoding (#41007) Removed the leniency when encoding remote reindex search requests that was introduced in 7.x. All index-names are now encoded before being sent to the remote host. Follow-up to #40303
2019-04-16 22:46:54 +08:00
include::migrate_8_0/reindex.asciidoc[]
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
include::migrate_8_0/api.asciidoc[]
include::migrate_8_0/rollup.asciidoc[]
Remove CommonTermsQuery and cutoff_frequency param (#42654) Remove `common` query and `cutoff_frequency` parameter of `match` and `multi_match` queries. Both have already been deprecated for the next 7.x version. Closes: #37096
2019-05-31 23:06:06 +08:00
include::migrate_8_0/search.asciidoc[]
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
include::migrate_8_0/security.asciidoc[]
Remove deprecated search.remote settings (#42381) We deprecated these settings awhile ago, in favor of cluster.remote. In 7.x we were gentle and provided automatic upgrade of these settings to the new settings. Now it is time for them to go. This commit removes the deprecated search.remote settings.
2019-05-23 23:06:07 +08:00
include::migrate_8_0/settings.asciidoc[]
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
include::migrate_8_0/snapshots.asciidoc[]
Remove fixed_auto_queue_size threadpool type (#52280) * Remove fixed_auto_queue_size threadpool type * Remove less * compilation fix * weaken assertion to accomodate tests that mock threadpool
2020-02-14 23:20:40 +08:00
include::migrate_8_0/threadpool.asciidoc[]
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828)
2020-04-29 04:40:50 +08:00
include::migrate_8_0/transport.asciidoc[]