[
https://issues.apache.org/jira/browse/SOLR-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036404#comment-14036404
]
Joel Bernstein commented on SOLR-6168:
--------------------------------------
Let's also consider how the recip() function query might be useful in a
situation where the ranges differ drastically as you describe.
for example:
{code}
fq={!collapse field=x max='sub(prod(field(y),10), recip(field(x),1,1000,1000))'}
{code}
> 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, 4.8.1
> Reporter: Umesh Prasad
> Assignee: Joel Bernstein
> Attachments: SOLR-6168-group-head-inconsistent-with-sort.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.8.1 revision number
> 1603061
> 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: [email protected]
For additional commands, e-mail: [email protected]
