You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Joel Bernstein (JIRA)" <ji...@apache.org> on 2014/02/19 14:42:27 UTC
[jira] [Resolved] (SOLR-5554) Ordering Issue when Collapsing using
min max
[ https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joel Bernstein resolved SOLR-5554.
----------------------------------
Resolution: Fixed
> Ordering Issue when Collapsing using min max
> --------------------------------------------
>
> Key: SOLR-5554
> URL: https://issues.apache.org/jira/browse/SOLR-5554
> Project: Solr
> Issue Type: Sub-task
> Components: search
> Affects Versions: 4.6
> Environment: Solr 4.6
> Reporter: Deepak Mishra
> Fix For: 4.7
>
> Attachments: DetailedErrorOnQuery6.txt, Error On Query4, Query1.txt, Query2.txt, Query3.txt, Query4.txt, Query5.txt, Query6.txt, SchemaDetails.txt
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org