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