You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Cassandra Targett (Jira)" <ji...@apache.org> on 2021/08/13 21:08:00 UTC

[jira] [Updated] (SOLR-12157) group.main ought to return group.ngroups as numFound and change start/rows semantics

     [ https://issues.apache.org/jira/browse/SOLR-12157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cassandra Targett updated SOLR-12157:
-------------------------------------
    Component/s: Grouping

> group.main ought to return group.ngroups as numFound and change start/rows semantics
> ------------------------------------------------------------------------------------
>
>                 Key: SOLR-12157
>                 URL: https://issues.apache.org/jira/browse/SOLR-12157
>             Project: Solr
>          Issue Type: Improvement
>          Components: Grouping
>            Reporter: David Smiley
>            Priority: Major
>         Attachments: groupToNormal.xsl
>
>
> I experimented with group=true (Result Grouping) in a product/SKU ecommerce scenario.  Ideally the client could be ignorant of the fact that the results are grouped when processing a grouped response (assuming it only needs the group heads and doesn't care how many matched per group).  It wants to see only the group head document, and have start/rows paging over them, and numFound to be the number of groups.  {{group.main}} doesn't do any of these things.  Is {{group.main}} actually useful to anyone right now?  If it's not; maybe we could change it (using some sort of back-compat mechanism like luceneVersion).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org