[ https://issues.apache.org/jira/browse/SOLR-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846229#comment-13846229 ]
Deepak Mishra commented on SOLR-5027: ------------------------------------- Hi Joel I context with the Shruti's comment. We faced the ordering issue without passing any sorting parameter and same filters in both queries. Query1 fq={!collapse field=company_id} Query2 fq={!collapse field=comany_id min=price} Query3 For debugging Query2, we added score field in fl=score,offering_id,company_id... That actually solved the document order issue Query4 But when we passed selective exclude in facet field of Query3, it give document in correct order but with NullPointerException in error and no facet (not the one in SOLR-5416). facet.field={!ex="samsung"}brand fq={!tag="samsung"}(brand:"samsung") The error is NullPointerException at org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852) Query5 Removing score from fl in Query 4 removes the error > 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.4#6159) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org