You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-commits@lucene.apache.org by Apache Wiki <wi...@apache.org> on 2012/01/06 11:28:03 UTC
[Solr Wiki] Update of "FieldCollapsing" by elonderin
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The "FieldCollapsing" page has been changed by elonderin:
http://wiki.apache.org/solr/FieldCollapsing?action=diff&rev1=38&rev2=39
Comment:
fix group.main:If true, the result of the last field grouping command is used as the main result list in the response, using group.format=simple
||sort||[sortspec]||How to sort the groups relative to each other. For example, {{{sort=popularity desc}}} will cause the groups to be sorted according to the highest popularity doc in each group. Defaults to "score desc".||
||group.sort||[sortspec]||How to sort documents within a single group. Defaults to the same value as the {{{sort}}} parameter.||
||group.format||grouped/simple||if simple, the grouped documents are presented in a single flat list. The start and rows parameters refer to numbers of documents instead of numbers of groups.||
- ||group.main||true/false||If true, the result of the first field grouping command is used as the main result list in the response, using group.format=simple||
+ ||group.main||true/false||If true, the result of the last field grouping command is used as the main result list in the response, using group.format=simple||
||group.ngroups||true/false||If true, includes the number of groups that have matched the query. Default is false.||
||group.truncate||true/false||If true, facet counts are based on the most relevant document of each group matching the query. Same applies for StatsComponent. Default is false. <!> [[Solr3.4]] Supported from Solr 3.4 and up.||
||group.cache.percent||[0-100]||If > 0 enables grouping cache. Grouping is executed actual two searches. This option caches the second search. A value of 0 disables grouping caching. Default is 0. Tests have shown that this cache only improves search time with boolean queries, wildcard queries and fuzzy queries. For simple queries like a term query or a match all query this cache has a negative impact on performance||