-
Notifications
You must be signed in to change notification settings - Fork 1.3k
RestStatusException detail in v4.3.0 #1995
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
thanks for pointing that out. I added the original exception's cause as the cause of the
|
sothawo
added a commit
to sothawo/spring-data-elasticsearch
that referenced
this issue
Nov 16, 2021
fixed in main and backported to 4.3.x. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I toyed with the idea of making this an SO post as I think I must be missing something, but at the moment it seems like an issue.
In the migration guide it is stated
No problem, and I understand the rational behind moving to this model, but I seem to be losing detail on the error exceptions.
i.e ElasticSearch 7.15.0 with Spring ES 4.3.0 sends a failing query
ES reponds with it's standard error response
but the
RestStatusException
that is surfaced seems to only contain the message"Elasticsearch exception [type=search_phase_execution_exception, reason=all shards failed]"
The good detail i.e. the bit
"No mapping found for [startEpoch] in order to sort on"
is not retrievable fromRestStatusException
infact anything other thattype
andreason
appears to have been lost.Should the original client specific exception, (
ElasticsearchStatusException
in my case) have been appended toRestStatusException
as the cause?The text was updated successfully, but these errors were encountered: