[
https://issues.apache.org/jira/browse/SOLR-12157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417666#comment-16417666
]
David Smiley commented on SOLR-12157:
-------------------------------------
Also, it'd be nice if the group info per group head could be returned using a
DocumentTransformer strategy rather than fundamentally changing the response
structure. In other words, do kinda like [child]. But this is definitely out
of scope to this issue.
> 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
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Priority: Major
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
