Hi Liu,
Aha now I see ... old format does not display that info. For faceting solution https://issues.apache.org/jira/browse/SOLR-2242 could be relevant. By the way how are these things in CollapsingQueryParser? https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-CollapsingQueryParser? On Thursday, January 2, 2014 6:07 AM, Liu Bo <diabl...@gmail.com> wrote: hi @Ahmet I've thought about using group.ngroups=true , but when you use group.main=true, there's no "ngroups" field in the response. and according to http://wiki.apache.org/solr/FieldCollapsing, the result might not be correct in solrcloud. I don't like using facet for this but seems have to... On 1 January 2014 00:35, Ahmet Arslan <iori...@yahoo.com> wrote: > Hi Tasmaniski, > > I don't follow. How come Liu's faceting workaround and n.groups=true > produce different results? > > > > > > > On Tuesday, December 31, 2013 6:08 PM, tasmaniski <tasmani...@gmail.com> > wrote: > @kamaci > Ofcourse. That is the problem. > > "group.limit is: the number of results (documents) to return for each > group." > NumFound is number of total found, but *not* sum number of *return for each > group.* > > @Liu Bo > seems to be the is only workaround for problem but > it's to much expensive to go through all the groups and calculate total > number of found/returned (I use PHP for client:) ). > > @iorixxx > Yes, I consider that (group.ngroups=true) > but in some group I have number of found result lesser than limit. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Grouping-results-with-group-limit-return-wrong-numFound-tp4108174p4108906.html > > Sent from the Solr - User mailing list archive at Nabble.com. > > -- All the best Liu Bo
