migrate_8_10.asciidoc 3.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889
  1. [[migrating-8.10]]
  2. == Migrating to 8.10
  3. ++++
  4. <titleabbrev>8.10</titleabbrev>
  5. ++++
  6. This section discusses the changes that you need to be aware of when migrating
  7. your application to {es} 8.10.
  8. See also <<release-highlights>> and <<es-release-notes>>.
  9. [discrete]
  10. [[breaking-changes-8.10]]
  11. === Breaking changes
  12. The following changes in {es} 8.10 might affect your applications
  13. and prevent them from operating normally.
  14. Before upgrading to 8.10, review these changes and take the described steps
  15. to mitigate the impact.
  16. There are no notable breaking changes in {es} 8.10.
  17. But there are some less critical breaking changes.
  18. [discrete]
  19. [[breaking_810_cluster_and_node_setting_changes]]
  20. ==== Cluster and node setting changes
  21. [[remove_unused_executor_builder_for_vector_tile_plugin]]
  22. .Remove the unused executor builder for vector tile plugin
  23. [%collapsible]
  24. ====
  25. *Details* +
  26. 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`'
  27. *Impact* +
  28. In the case the threadpool appears on the yaml file, Elasticsearch will not start until those lines are removed.
  29. ====
  30. [discrete]
  31. [[breaking_810_java_api_changes]]
  32. ==== Java API changes
  33. [[change_pre_configured_cached_analyzer_components_to_use_indexversion_instead_of_version-highlight]]
  34. .Change pre-configured and cached analyzer components to use IndexVersion instead of Version
  35. [%collapsible]
  36. ====
  37. *Details* +
  38. This PR changes the types used to obtain pre-configured components from Version to IndexVersion,
  39. with corresponding changes to method names.
  40. Prior to 8.10, there is a one-to-one mapping between node version and index version, with corresponding constants
  41. in the IndexVersion class.
  42. Starting in 8.10, IndexVersion is versioned independently of node version, and will be a simple incrementing number.
  43. For more information on how to use IndexVersion and other version types, please see the contributing guide.
  44. *Impact* +
  45. Analysis components now take IndexVersion instead of Version
  46. ====
  47. [discrete]
  48. [[deprecated-8.10]]
  49. === Deprecations
  50. The following functionality has been deprecated in {es} 8.10
  51. and will be removed in a future version.
  52. While this won't have an immediate impact on your applications,
  53. we strongly encourage you to take the described steps to update your code
  54. after upgrading to 8.10.
  55. To find out if you are using any deprecated functionality,
  56. enable <<deprecation-logging, deprecation logging>>.
  57. [discrete]
  58. [[deprecations_810_authorization]]
  59. ==== Authorization deprecations
  60. [[mark_apm_user_for_removal_in_future_major_release]]
  61. .Mark `apm_user` for removal in a future major release
  62. [%collapsible]
  63. ====
  64. *Details* +
  65. The `apm_user` role has been deprecated and will be removed in a future major release. Users should migrate to `editor` and `viewer` roles
  66. *Impact* +
  67. Users will have to migrate to `editor` and `viewer` roles
  68. ====