forked from elastic/elasticsearch
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] Add a deprecation warning that the JSON format of non-detailed …
…errors is changing in v9 (elastic#116330) (elastic#114739)
- Loading branch information
Showing
29 changed files
with
108 additions
and
57 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
pr: 114739 | ||
summary: Add a basic deprecation warning that the JSON format for non-detailed error responses is changing in v9 | ||
area: Infra/REST API | ||
type: deprecation | ||
issues: [89387] | ||
deprecation: | ||
title: The format of non-detailed error responses is changing in v9 | ||
area: REST API | ||
details: |- | ||
When an error occurs when processing a request, Elasticsearch returns information on that error in the REST response. | ||
If `http:detailed_errors.enabled: false` is specified in node settings with the v8 REST API and below, | ||
the format of this response changes significantly. | ||
Starting with the v9 REST API, the JSON structure of responses with errors when the `http.detailed_errors.enabled: false` option is set | ||
will be the same as when detailed errors are enabled (which is the default). | ||
To keep using the existing format for non-detailed error responses, use the v8 REST API. | ||
impact: |- | ||
If you have set `http.detailed_errors.enabled: false` (the default is `true`) | ||
the structure of JSON when any exceptions occur will change with the v9 REST API. | ||
To keep using the existing format, use the v8 REST API. | ||
notable: false |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.