[
https://issues.apache.org/jira/browse/SOLR-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036857#comment-14036857
]
Umesh Prasad commented on SOLR-6168:
------------------------------------
Hi Joel,
Sure. we can take this forward on mailing list.
To be explicit :
1. min/max param is equivalent to group.sort (both pick up the group heads)
2. group.sort defaults to sort if not specified. (standard collapsing)
3. min/max defaults to score if not specified (CollapsingQParser)
4. sort defaults to score if not specified and grouping is on ( as per
https://cwiki.apache.org/confluence/display/solr/Result+Grouping)
This is a very important difference.
So something like sort = seller_rank asc, ratings desc, function_query desc,
popularity desc, score desc might end up giving completely different results.
> 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]
