lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Umesh Prasad (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-6168) CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used
Date Sat, 14 Jun 2014 07:07:01 GMT

     [ https://issues.apache.org/jira/browse/SOLR-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Umesh Prasad updated SOLR-6168:
-------------------------------

    Attachment: SOLR-6168-broken-sort-test-case.patch

This shows the broken sort with 3 or more params.


> CollapsingQParserPlugin ranks incorrectly when 3 or more sort params are used
> -----------------------------------------------------------------------------
>
>                 Key: SOLR-6168
>                 URL: https://issues.apache.org/jira/browse/SOLR-6168
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.7.1
>            Reporter: Umesh Prasad
>         Attachments: SOLR-6168-broken-sort-test-case.patch
>
>
> CollapsingQParser Plugin ranks documents incorrectly when more than 2 sort fields are
used.
>    I have attached a test case, which demonstrates the broken behavior when 3 sort fields
are used.
> The failing test case patch is against Lucene/Solr 4.7 revision  number 1602388
> PS :     SOLR-5408 fixed the issue with sorting only for two sort fields, by allowing
one to specify max/min=<field-name>. However that requires 2nd sort field to be a numeric
field. It will not work with string field or function query sort.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message