You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following request produces a SearchParseException because there is no aggregator of type foo:
GET _search
{
"aggs": {
"foo": {
"bar": {}
}
}
}
On the current master this is masked by a StackOverflowError (I presume as the stack trace fall off the top of the console buffer) will the follow (part) stacktrace showing the infinite loop:
at org.elasticsearch.ElasticsearchException.toXContent(ElasticsearchException.java:277)
at org.elasticsearch.ElasticsearchException.toXContent(ElasticsearchException.java:312)
at org.elasticsearch.ElasticsearchException.toXContent(ElasticsearchException.java:277)
at org.elasticsearch.ElasticsearchException.toXContent(ElasticsearchException.java:312)
at org.elasticsearch.ElasticsearchException.toXContent(ElasticsearchException.java:277)
at org.elasticsearch.ElasticsearchException.toXContent(ElasticsearchException.java:312)
at org.elasticsearch.ElasticsearchException.toXContent(ElasticsearchException.java:277)
at org.elasticsearch.ElasticsearchException.toXContent(ElasticsearchException.java:312)
at org.elasticsearch.ElasticsearchException.toXContent(ElasticsearchException.java:277)
at org.elasticsearch.ElasticsearchException.toXContent(ElasticsearchException.java:312)
at org.elasticsearch.ElasticsearchException.toXContent(ElasticsearchException.java:277)
at org.elasticsearch.ElasticsearchException.toXContent(ElasticsearchException.java:312)
at org.elasticsearch.ElasticsearchException.toXContent(ElasticsearchException.java:277)
The text was updated successfully, but these errors were encountered:
SearchParseException extends SearchException which in turn extends ElasticsearchException and implements ElasticsearchWrapperException. Any exception which extends ElasticsearchException and implements ElasticsearchWrapperExceptionwill suffer this issue
the specialization can cause stack overflows if an exception is a
ElasticsearchWrapperException as well as a ElasticsearchException.
This commit just relies on the unwrap logic now to find the cause and only
renders if we the rendering exception is the cause otherwise forwards
to the generic exception rendering.
Closeselastic#11994
The following request produces a SearchParseException because there is no aggregator of type
foo
:On the current master this is masked by a StackOverflowError (I presume as the stack trace fall off the top of the console buffer) will the follow (part) stacktrace showing the infinite loop:
The text was updated successfully, but these errors were encountered: