You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2013/10/28 20:12:32 UTC
[jira] [Comment Edited] (SOLR-5027) Field Collapsing PostFilter
[ https://issues.apache.org/jira/browse/SOLR-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807125#comment-13807125 ]
Steve Rowe edited comment on SOLR-5027 at 10/28/13 7:12 PM:
------------------------------------------------------------
[~er.shruti], the problem is that as of Lucene/Solr 4.6, all ivy.xml versions are pulled from {{lucene/ivy-versions.properties}} - see LUCENE-5249 and LUCENE-5257 - but not in the lucene_solr_4_5 branch.
You can look up the correct ivy.xml version to use in the 4.6 branch, rather than the {{/com.carrotsearch/hppc}} thing that's on branch_4x.
was (Author: steve_rowe):
[~er.shruti], the problem is that as of Lucene/Solr 4.6, all ivy.xml versions are pulled from {{lucene/ivy-versions.properties}} - see LUCENE-5249 and LUCENE-5247 - but not in the lucene_solr_4_5 branch.
You can look up the correct ivy.xml version to use in the 4.6 branch, rather than the {{/com.carrotsearch/hppc}} thing that's on branch_4x.
> Field Collapsing PostFilter
> ---------------------------
>
> Key: SOLR-5027
> URL: https://issues.apache.org/jira/browse/SOLR-5027
> Project: Solr
> Issue Type: New Feature
> Components: search
> Affects Versions: 5.0
> Reporter: Joel Bernstein
> Assignee: Joel Bernstein
> Priority: Minor
> Fix For: 4.6, 5.0
>
> Attachments: SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch
>
>
> This ticket introduces the *CollapsingQParserPlugin*
> The *CollapsingQParserPlugin* is a PostFilter that performs field collapsing. This is a high performance alternative to standard Solr field collapsing (with *ngroups*) when the number of distinct groups in the result set is high.
> For example in one performance test, a search with 10 million full results and 1 million collapsed groups:
> Standard grouping with ngroups : 17 seconds.
> CollapsingQParserPlugin: 300 milli-seconds.
> Sample syntax:
> Collapse based on the highest scoring document:
> {code}
> fq=(!collapse field=<field_name>}
> {code}
> Collapse based on the min value of a numeric field:
> {code}
> fq={!collapse field=<field_name> min=<field_name>}
> {code}
> Collapse based on the max value of a numeric field:
> {code}
> fq={!collapse field=<field_name> max=<field_name>}
> {code}
> Collapse with a null policy:
> {code}
> fq={!collapse field=<field_name> nullPolicy=<null_policy>}
> {code}
> There are three null policies:
> ignore : removes docs with a null value in the collapse field (default).
> expand : treats each doc with a null value in the collapse field as a separate group.
> collapse : collapses all docs with a null value into a single group using either highest score, or min/max.
> The CollapsingQParserPlugin also fully supports the QueryElevationComponent
> *Note:* The July 16 patch also includes and ExpandComponent that expands the collapsed groups for the current search result page. This functionality will be moved to it's own ticket.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org