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

Christine Poerschke resolved SOLR-16217.
----------------------------------------
    Fix Version/s: 9.1
                   main (10.0)
       Resolution: Fixed

> SortingMergePolicy: test coverage for dual-field sort
> -----------------------------------------------------
>
>                 Key: SOLR-16217
>                 URL: https://issues.apache.org/jira/browse/SOLR-16217
>             Project: Solr
>          Issue Type: Test
>            Reporter: Christine Poerschke
>            Assignee: Christine Poerschke
>            Priority: Minor
>             Fix For: 9.1, main (10.0)
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> SOLR-5730 previously made Lucene's {{SortingMergePolicy}} configurable in 
> Solr.
> The sort criteria could be (say) {{timestamp_i_dvo desc}} or (say) 
> {{timestamp_i_dvo desc, id desc}} with the latter using the unique document 
> key to ensure deterministic sorting.
> See e.g. 
> [https://github.com/apache/solr/blob/releases/solr/9.0.0/solr/core/src/java/org/apache/solr/search/SolrIndexSearcher.java#L193]
>  and 
> [https://github.com/apache/solr/blob/releases/solr/9.0.0/solr/core/src/java/org/apache/solr/search/EarlyTerminatingSortingCollector.java#L55-L67]
>  w.r.t. {{segmentTerminateEarly}} logic detail i.e. single-field 
> {{sort=timestamp_i_dvo desc}} could be used if the merge policy has 
> dual-field {{timestamp_i_dvo desc, id desc}} but dual-field sort requires 
> dual-field merge policy.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to