[ 
https://issues.apache.org/jira/browse/SOLR-9104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034358#comment-16034358
 ] 

Matthias Krueger commented on SOLR-9104:
----------------------------------------

[~markus.jel...@openindex.io]: See comment from [~hossman] here or mine on 
SOLR-8807. It seems that two Collapse-Filters just don't work if there are 
documents returned from less than all segments. A quick fix seems to be to call 
{{super.doSetNextReader(context)}} as first thing in all of 
CollapsingQParserPlugin's DelegatingCollectors' {{doSetNextReaders}} but I 
don't know if this has any undesired side effects.

> NPE in CollapsingQParser when two fq={!collapse} and zero results
> -----------------------------------------------------------------
>
>                 Key: SOLR-9104
>                 URL: https://issues.apache.org/jira/browse/SOLR-9104
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 6.0
>            Reporter: Markus Jelsma
>             Fix For: 6.2, master (7.0)
>
>
> This is a very weird problem that is reproducible on a small production 
> server, but not on the local machine although they run the same 6.0 version., 
> and have an almost identical index. The only minor difference is that 
> production is a SolrCloud with 1 shard and two replica's, just for a bit of 
> redundancy.
> The following query yields zero results and throws the NPE:
> {code}
> select?q=query:seis&fq={!collapse field=query_digest}&fq={!collapse 
> field=result_digest}
> {code}
> The next query does yield results and does not throw anything, it just works 
> as it should work:
> {code}
> select?q=query:seiz&fq={!collapse field=query_digest}&fq={!collapse 
> field=result_digest}
> {code}
> The /select handler used does not add any fancy param other than rows.
> Here's the NPE:
> {code}
> 2016-05-11 14:10:27.666 ERROR (qtp1209271652-3338) [c:suggestions s:shard1 
> r:core_node1 x:suggestions_shard1_replica1] o.a.s.s.HttpSolrCall 
> null:java.lang.NullPointerException
>         at 
> org.apache.solr.search.CollapsingQParserPlugin$IntScoreCollector.finish(CollapsingQParserPlugin.java:814)
>         at 
> org.apache.solr.search.CollapsingQParserPlugin$IntScoreCollector.finish(CollapsingQParserPlugin.java:851)
>         at 
> org.apache.solr.search.SolrIndexSearcher.buildAndRunCollectorChain(SolrIndexSearcher.java:272)
>         at 
> org.apache.solr.search.SolrIndexSearcher.getDocListNC(SolrIndexSearcher.java:1794)
>         at 
> org.apache.solr.search.SolrIndexSearcher.getDocListC(SolrIndexSearcher.java:1611)
>         at 
> org.apache.solr.search.SolrIndexSearcher.search(SolrIndexSearcher.java:634)
>         at 
> org.apache.solr.handler.component.QueryComponent.process(QueryComponent.java:529)
>         at 
> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:287)
>         at 
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:155)
> {code}
> Edit: for the sake of clarity. It really needs double fq={!collapse bla bla 
> for the NPE to appear. If i remove either of the filters from the query, i 
> get a nice zero resultset back. Both fields are defined as int.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to