-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
Output a consistent format when generating error json #90529
base: main
Are you sure you want to change the base?
Conversation
Now, error fields will always have 'type' and 'reason' fields, and the information in those fields is the same regardless of whether the output is detailed or not
Pinging @elastic/es-core-infra (Team:Core/Infra) |
Hi @thecoop, I've created a changelog YAML for you. |
Note this does have some BwC concerns, as this changes the output format when not detailed, but from #89387 we consider the current behaviour a bug |
237ef12
to
cec444a
Compare
server/src/test/java/org/elasticsearch/ElasticsearchExceptionTests.java
Outdated
Show resolved
Hide resolved
Hi @thecoop, I've updated the changelog YAML for you. |
Hi @thecoop, I've updated the changelog YAML for you. |
Hi @thecoop, I've updated the changelog YAML for you. Note that since this PR is labelled |
071c718
to
2a7fda6
Compare
2a7fda6
to
750eb7d
Compare
This PR is marked as a "breaking" change. Is it really a breaking change? |
This reverts commit 459acf4.
Hi @thecoop, I've updated the changelog YAML for you. Note that since this PR is labelled |
@elasticmachine update branch |
Now, error fields will always have 'type' and 'reason' fields, and the information in those fields is the same regardless of whether the output is detailed or not
This fixes #89387