The Grouping feature only works if groups are in the same shard.
Perhaps that is the problem here?

I could find https://issues.apache.org/jira/browse/SOLR-4164 which
says that once the sharding was fixed, the problem went away. We
should come up with a better exception message though.

On Fri, Mar 21, 2014 at 10:49 PM, Ugo Matrangolo
<ugo.matrang...@gmail.com> wrote:
> Hi,
>
> I have a two shard collection running and I'm getting this error on each
> query:
>
> 2014-03-21 17:08:42,018 [qtp-75] ERROR
> org.apache.solr.servlet.SolrDispatchFilter  -
> *null:java.lang.IllegalArgumentException:
> numHits must be > 0; please use TotalHitCountCollector if you just need the
> total hit count*
>         at
> org.apache.lucene.search.TopFieldCollector.create(TopFieldCollector.java:1130)
>         at
> org.apache.lucene.search.TopFieldCollector.create(TopFieldCollector.java:1079)
>         at
> org.apache.lucene.search.grouping.AbstractSecondPassGroupingCollector.<init>(AbstractSecondPassGroupingCollector.java:75)
>         at
> org.apache.lucene.search.grouping.term.TermSecondPassGroupingCollector.<init>(TermSecondPassGroupingCollector.java:49)
>         at
> org.apache.solr.search.grouping.distributed.command.TopGroupsFieldCommand.create(TopGroupsFieldCommand.java:129)
>         at
> org.apache.solr.search.grouping.CommandHandler.execute(CommandHandler.java:142)
>         at
> org.apache.solr.handler.component.QueryComponent.process(QueryComponent.java:387)
>         at
> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:214)
>         at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
>         at org.apache.solr.core.SolrCore.execute(SolrCore.java:1916)
>         at
> org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:780)
>
> Note that I'm using grouping and disabling it fixed the problem.
>
> I was aware that SolrCloud does not fully supports grouping in a
> distributed setup but I was expecting incorrect results (that have to
> addressed with custom hashing afaik) and not an error.
>
> Does anyone see this error before?
>
> Ugo



-- 
Regards,
Shalin Shekhar Mangar.

Reply via email to