Christine Poerschke commented on SOLR-9643:

Hello [~parasdiwan] - you don't mention whether or not your collection is 
sharded, if it is sharded then the [Distributed Result Grouping 
 might apply to the behaviour you observe i.e.
bq. ... {{group.ngroups}} and {{group.facet}} require that all documents in 
each group must be co-located on the same shard in order for accurate counts to 
be returned. ...

> Pagination issue occurs in solr cloud when results are grouped on a field
> -------------------------------------------------------------------------
>                 Key: SOLR-9643
>                 URL: https://issues.apache.org/jira/browse/SOLR-9643
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>    Affects Versions: 6.1
>         Environment: Solr cloud is deployed on AWS linux server. 4 Solr 
> servers and apache zookeeper is setup
>            Reporter: Paras Diwan
>            Priority: Critical
>             Fix For: 6.1.1
> Either value of ngroups in grouped query is inaccurate or there is some issue 
> in returning documents of later pages. 
> select?q=*:*&group=true&group.field=family&group.ngroups=true&start=0&group.limit=1
> For above mentioned query i get ngroups = 396324
> but for the same query when i modify start to 396320. it returns 0 docs, an 
> empty page.
> Instead the last result is at 386887.
> Please look into this issue or offer some solution 

This message was sent by Atlassian JIRA

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

Reply via email to