migrate_8_17.asciidoc 2.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  1. [[migrating-8.17]]
  2. == Migrating to 8.17
  3. ++++
  4. <titleabbrev>8.17</titleabbrev>
  5. ++++
  6. This section discusses the changes that you need to be aware of when migrating
  7. your application to {es} 8.17.
  8. See also <<release-highlights>> and <<es-release-notes>>.
  9. coming::[8.17.0]
  10. [discrete]
  11. [[breaking-changes-8.17]]
  12. === Breaking changes
  13. There are no breaking changes in {es} 8.17.
  14. [discrete]
  15. [[deprecated-8.17]]
  16. === Deprecations
  17. The following functionality has been deprecated in {es} 8.17
  18. and will be removed in a future version.
  19. While this won't have an immediate impact on your applications,
  20. we strongly encourage you to take the described steps to update your code
  21. after upgrading to 8.17.
  22. To find out if you are using any deprecated functionality,
  23. enable <<deprecation-logging, deprecation logging>>.
  24. [discrete]
  25. [[deprecations_817_mapping]]
  26. ==== Mapping deprecations
  27. [[deprecate_source_mode_in_mappings]]
  28. .Deprecate `_source.mode` in mappings
  29. [%collapsible]
  30. ====
  31. *Details* +
  32. Configuring `_source.mode` in mappings is deprecated and will be removed in future versions. Use `index.mapping.source.mode` index setting instead.
  33. *Impact* +
  34. Use `index.mapping.source.mode` index setting instead
  35. ====
  36. [discrete]
  37. [[deprecations_817_rest_api]]
  38. ==== REST API deprecations
  39. [[format_of_non_detailed_error_responses_changing_in_v9]]
  40. .The format of non-detailed error responses is changing in v9
  41. [%collapsible]
  42. ====
  43. *Details* +
  44. When an error occurs when processing a request, Elasticsearch returns information on that error in the REST response.
  45. If `http:detailed_errors.enabled: false` is specified in node settings with the v8 REST API and below,
  46. the format of this response changes significantly.
  47. Starting with the v9 REST API, the JSON structure of responses with errors when the `http.detailed_errors.enabled: false` option is set
  48. will be the same as when detailed errors are enabled (which is the default).
  49. To keep using the existing format for non-detailed error responses, use the v8 REST API.
  50. *Impact* +
  51. If you have set `http.detailed_errors.enabled: false` (the default is `true`)
  52. the structure of JSON when any exceptions occur will change with the v9 REST API.
  53. To keep using the existing format, use the v8 REST API.
  54. ====