-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[8.x] Add a basic deprecation warning that the JSON format is changing in v9 (#116330) #114739
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
a00cc1d
Add a basic deprecation warning that the JSON format is changing in v9
thecoop d255ce6
Some more test fixes
thecoop 95baef8
Merge branch '8.x' into exception-json-warning
elasticmachine 2a0d87d
Merge remote-tracking branch 'upstream/8.x' into exception-json-warning
thecoop a6e6843
Merge branch '8.x' into exception-json-warning
elasticmachine 608d9df
Add changelog entry for the deprecation
thecoop 82f23e1
Only log deprecation warning when error actually happens
thecoop 4580d7f
Update changelog
thecoop 879e984
Get the check the right way round
thecoop ffd4b7b
Merge remote-tracking branch 'upstream/8.x' into exception-json-warning
thecoop c77a7e1
Update changelog
thecoop File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.