lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "bronco (Created) (JIRA)" <>
Subject [jira] [Created] (SOLR-2817) Search result with grouping activated delivers wrong numFound values.
Date Fri, 07 Oct 2011 04:00:29 GMT
Search result with grouping activated delivers wrong numFound values.

                 Key: SOLR-2817
             Project: Solr
          Issue Type: Bug
    Affects Versions: 3.4
            Reporter: bronco
            Priority: Blocker

I use the 3.4 brach of solr for grouping my results, but obviously there is something wrong
in my eyes. If I activate the grouping functionality I get the expected results. In my case
for example 4 rows, but the the numFound value says it has 26 results. 

This result is used by the Apache Solr Library in Drupal to calculate the correct pager on
my website. Now I get a search result page with 4 results and a confused pager with 3 more
steps to not existing search pages.

I try a lot of things including using a facet and all the other suggested things by google
but I couldn't change the numFound value to the correct one in my case.

If I not use the group.main=true setting including a facet I get in the facet conclusion the
correct values of found results but it also say matches 6 (numFound=6). The Apache Solr Library
make it nesessary to use the group.main=true setting because without this value the library
is not able to parse the resultset. So I get always an empty website without any results even
solr answers correctly.

Is it somehow possible to change the numFound value to the correct one of the group count
result. I think nobody groups a field and shows maybe 10 entries which belong to the request
and tell the user we have 200 other things which are not interesting you. But I have to tell

Any help is apreciated to get some understanding why solr delivers me this numFound result
and how to fix this issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message