[
https://issues.apache.org/jira/browse/SOLR-8851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221636#comment-15221636
]
Marius Grama commented on SOLR-8851:
------------------------------------
[[email protected]] indeed the ticket is a duplicate of SOLR-7864 .
The patch that you have recommended on SOLR-7864 doesn't take into account
that, in some situations, (like the terms query mentioned in my comment above)
is not needed. Wouldn't it make more sense to add the response/explaint/...
elements in the _prepare_ phase of the
org.apache.solr.handler.component.SearchComponent implementations and fill them
during the _process_ phase ?
> ClassCastException in SearchHandler
> -----------------------------------
>
> Key: SOLR-8851
> URL: https://issues.apache.org/jira/browse/SOLR-8851
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.4.1
> Reporter: Pascal Chollet
>
> When there is a query timeout in non-distrub mode, {{SearchHandler}} is
> throwing a {{ClassCastException}}:
> {code}java.lang.ClassCastException: org.apache.solr.response.ResultContext
> cannot be cast to org.apache.solr.common.SolrDocumentList
> at
> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:293)
> at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:156)
> ...{code}
> The problem can be reproduced if any component running after
> {{QueryComponent}} times out - in our case it is {{FacetComponent}} which
> throws a {{ExitingReaderException}}.
> {{SearchHandler:293}} expects a {{SolrDocumentList}} in {{rsp.response}}, but
> {{QueryComponent}} did add a {{ResultContext}} instead.
> It looks like this is not a problem, if the {{QueryComponent}} itself is
> timing out, as rsp.response is null in that case. It's only a problem if a
> component after {{QueryComponent}} is timing out.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
