The group head is the document from each group that was selected during the collapse. Only the group heads remain in the result set following the collapse. It looks like in the example above you have the basic idea correct.
Joel Bernstein http://joelsolr.blogspot.com/ On Sat, Jun 20, 2015 at 12:40 AM, Derek Poh <d...@globalsources.com> wrote: > Hi Joel > > By group heads, is it referring to the document thatis use to represent > each group in the main result section? > > Eg. Using the below 3 documentsandwe collapse on field supplier_id > > supplier_id:S1 > product_id:P1 > > supplier_id:S2 > product_id:P2 > > supplier_id:S2 > product_id:P3 > > With collapse on supplier_id, the result in the main sectionis as follows, > > supplier_id:S1 > product_id:P1 > > supplier_id:S2 > product_id:P3 > > The group head of supplier_id:S1 is P1and supplier_id:S2 will be P3? > > Facets (and even sort) are calculated on P1 and P3? > > -Derek > > > On 6/19/2015 7:05 PM, Joel Bernstein wrote: > >> The CollapsingQParserPlugin currently doesn't calculate facets at all. It >> simply collapses the document set. The facets are then calculated only on >> the group heads. >> >> Grouping has special faceting code built into it that supports the >> group.facet functionality. >> >> Joel Bernstein >> http://joelsolr.blogspot.com/ >> >> On Fri, Jun 19, 2015 at 6:20 AM, Derek Poh <d...@globalsources.com> >> wrote: >> >> Hi >>> >>> I read about "collapsingQParser returns the facet count the same as >>> group.truncate=true" and has this issue with the facet count and the >>> after >>> filter facet count notthe same. >>> Using group.facetdoes not has this issue but it's performance is very >>> badcompared to collapsingQParser. >>> >>> I trying to understand why collapsingQParser behave this way and will >>> need >>> to explain to management. >>> >>> Can someone explain how collapsingQParser calculatethefacet >>> countscompated >>> to group.facet? >>> >>> Thank you, >>> Derek >>> >>> >>> >>> >
