Thanks Martijn - I should be able to patch the Solr 3.3 release based on r1145748.
- Nikhil ________________________________ From: Martijn v Groningen To: solr-user@lucene.apache.org; Nikhil Chhaochharia Sent: Wednesday, 13 July 2011 2:04 AM Subject: Re: Possible bug in Solr 3.3 grouping Hi Nikhil, Thanks for raising this issue. I checked this particular issue in a test case and I ran into the same error, so this is indeed a bug. I've fixed this issue for 3x in revision 1145748. So checking out the latest 3x branch and building Solr yourself should give you this bug fix. Or you can wait until the 3x build produces new nightly artifacts: https://builds.apache.org/job/Solr-3.x/lastSuccessfulBuild/artifact/artifacts/ The numFound in your case is based on number of documents, not groups. So you might still get an empty result, because there might be less than 40 groups in this result set. You can see the number of groups by using the group.ngroups=true parameter this includes the number of groups, but the the group.format must be grouped otherwise you don't get the number of groups in the response. Martijn On 12 July 2011 09:00, Nikhil Chhaochharia <nikhil...@yahoo.com> wrote: Hi, > >I am using Solr 3.3 and have run into a problem with grouping. If >'group.main' is 'true' and 'start' is greater than 'rows', then I do not get >any results. A sample response is: > ><response> ><lst name="responseHeader"><int name="status">0</int><int >name="QTime">602</int></lst><lst name="grouped"/><result name="response" >numFound="2239538" start="40" maxScore="6.140459"/> ></response> > > >If 'group.main' is false, then I get results. > >Did anyone else come across this problem? Using the grouping feature with >pagination of results will make start > rows from the third page onwards. > >Thanks, >Nikhil > >
