[
https://issues.apache.org/jira/browse/SOLR-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036056#comment-14036056
]
Umesh Prasad commented on SOLR-6168:
------------------------------------
Hi Joel,
Actually the issue is with Collapsing picking up group head. which is
inconsistent with original grouping implementation. (manually verified). We
have been using solr's grouping specification for collapsing our search results
and it picks up the group head which would have come first as per sorting.
The trick to combine fields with sum/exponential etc will not work if
field1 and field2's range differ drastically. Which is true for my case.
PS :
1.The original test case is incorrect. I am replacing it with another test case
patch.
2. I have made progress by creating array of FieldValueCollapse from
sort/min/max spec. Trying to get all test cases to work. Will attach it once
ready.
> 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-broken-multi-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.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]
