mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-24 23:27:25 -04:00
89 lines
3 KiB
Text
89 lines
3 KiB
Text
[[migrating-8.10]]
|
|
== Migrating to 8.10
|
|
++++
|
|
<titleabbrev>8.10</titleabbrev>
|
|
++++
|
|
|
|
This section discusses the changes that you need to be aware of when migrating
|
|
your application to {es} 8.10.
|
|
|
|
See also <<release-highlights>> and <<es-release-notes>>.
|
|
|
|
[discrete]
|
|
[[breaking-changes-8.10]]
|
|
=== Breaking changes
|
|
|
|
The following changes in {es} 8.10 might affect your applications
|
|
and prevent them from operating normally.
|
|
Before upgrading to 8.10, review these changes and take the described steps
|
|
to mitigate the impact.
|
|
|
|
|
|
There are no notable breaking changes in {es} 8.10.
|
|
But there are some less critical breaking changes.
|
|
|
|
[discrete]
|
|
[[breaking_810_cluster_and_node_setting_changes]]
|
|
==== Cluster and node setting changes
|
|
|
|
[[remove_unused_executor_builder_for_vector_tile_plugin]]
|
|
.Remove the unused executor builder for vector tile plugin
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
The threadpool called `vectortile` is a left over from the original development of the vector tile search end point and it is used nowhere. It can still be a breaking change if it is configured on the elasticsearch yml file, for example by changing the threadpool size `thread_pool.vectortile.size=8`'
|
|
|
|
*Impact* +
|
|
In the case the threadpool appears on the yaml file, Elasticsearch will not start until those lines are removed.
|
|
====
|
|
|
|
[discrete]
|
|
[[breaking_810_java_api_changes]]
|
|
==== Java API changes
|
|
|
|
[[change_pre_configured_cached_analyzer_components_to_use_indexversion_instead_of_version-highlight]]
|
|
.Change pre-configured and cached analyzer components to use IndexVersion instead of Version
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
This PR changes the types used to obtain pre-configured components from Version to IndexVersion,
|
|
with corresponding changes to method names.
|
|
|
|
Prior to 8.10, there is a one-to-one mapping between node version and index version, with corresponding constants
|
|
in the IndexVersion class.
|
|
Starting in 8.10, IndexVersion is versioned independently of node version, and will be a simple incrementing number.
|
|
For more information on how to use IndexVersion and other version types, please see the contributing guide.
|
|
|
|
*Impact* +
|
|
Analysis components now take IndexVersion instead of Version
|
|
====
|
|
|
|
|
|
[discrete]
|
|
[[deprecated-8.10]]
|
|
=== Deprecations
|
|
|
|
The following functionality has been deprecated in {es} 8.10
|
|
and will be removed in a future version.
|
|
While this won't have an immediate impact on your applications,
|
|
we strongly encourage you to take the described steps to update your code
|
|
after upgrading to 8.10.
|
|
|
|
To find out if you are using any deprecated functionality,
|
|
enable <<deprecation-logging, deprecation logging>>.
|
|
|
|
[discrete]
|
|
[[deprecations_810_authorization]]
|
|
==== Authorization deprecations
|
|
|
|
[[mark_apm_user_for_removal_in_future_major_release]]
|
|
.Mark `apm_user` for removal in a future major release
|
|
[%collapsible]
|
|
====
|
|
*Details* +
|
|
The `apm_user` role has been deprecated and will be removed in a future major release. Users should migrate to `editor` and `viewer` roles
|
|
|
|
*Impact* +
|
|
Users will have to migrate to `editor` and `viewer` roles
|
|
====
|
|
|