[
https://issues.apache.org/jira/browse/SOLR-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096935#comment-13096935
]
Martijn van Groningen commented on SOLR-2066:
---------------------------------------------
bq. I noticed that when merging TopGroups it's stated that totalGroupCount
cannot be merged, but wouldn't it just be a matter of adding up the numbers
(since groups shouldn't overlap across shards)
If group.ngroups is specified we can just add the total group count together,
but the Solr user is then responsible for making sure that the documents
belonging to a group end up in the same shard. If this is not done, then the
group counts will be incorrect.
bq. I'm probably missing something, but having a total number of groups - also
across shards - is a tremendous help for paging; despite the performance
penalty involved.
All shards need to send all the unique groups over the wire to the shard the is
responsible for the group merging. For indices with a lot a of unique groups
this will be very expensive. In the current solution only the top N groups (N
being equals to rows param) are sent over the wire from the individual shards
to the shard that is responsible for the group merging.
> Search Grouping: support distributed search
> -------------------------------------------
>
> Key: SOLR-2066
> URL: https://issues.apache.org/jira/browse/SOLR-2066
> Project: Solr
> Issue Type: Sub-task
> Reporter: Yonik Seeley
> Fix For: 3.4, 4.0
>
> Attachments: SOLR-2066.patch, SOLR-2066.patch, SOLR-2066.patch,
> SOLR-2066.patch, SOLR-2066.patch, SOLR-2066.patch
>
>
> Support distributed field collapsing / search grouping.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
