[
https://issues.apache.org/jira/browse/SOLR-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796750#comment-13796750
]
Joel Bernstein commented on SOLR-5027:
--------------------------------------
I had problems applying this patch to 4.2.1 as well. The patch is applied from
the Lucene/Solr root below. You'll see though that my errors are different.
There are two files ivy.xml and QParserPlugin.java that are different enough
that the patch did not apply. I'm not sure exactly the issue with your error.
I'll see if I can create a patch that will work with 4.2.1.
$ patch -p0 < SOLR-5027.patch
patching file solr/core/ivy.xml
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file solr/core/ivy.xml.rej
patching file
solr/core/src/test/org/apache/solr/search/TestCollapseQParserPlugin.java
patching file solr/core/src/test/org/apache/solr/search/QueryEqualityTest.java
patching file
solr/core/src/test-files/solr/collection1/conf/solrconfig-collapseqparser.xml
patching file
solr/core/src/java/org/apache/solr/search/CollapsingQParserPlugin.java
patching file solr/core/src/java/org/apache/solr/search/QParserPlugin.java
Hunk #1 FAILED at 51.
1 out of 1 hunk FAILED -- saving rejects to file
solr/core/src/java/org/apache/solr/search/QParserPlugin.java.rej
> 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: [email protected]
For additional commands, e-mail: [email protected]
