[
https://issues.apache.org/jira/browse/SOLR-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119125#comment-15119125
]
Shai Erera commented on SOLR-5730:
----------------------------------
I don't think that we need to change all MPs to MPFs. If you encounter an MP,
you parse it as usual (this is also needed for back-compat). If someone defines
an explicit MPF, we use it. For now (this issue that is), we just implement a
SortingMergePolicyFactory. For the "flat" MP, we can create a simple FlatMPF or
ImplicitMPF (or whatever) that will parse the MP out of solrconfig.xml.
I think that if we proceed with this issue before we have MPF, then we'll need
to support both single MP, chained MP and MPF, which I don't think we want?
> make Lucene's SortingMergePolicy and EarlyTerminatingSortingCollector
> configurable in Solr
> ------------------------------------------------------------------------------------------
>
> Key: SOLR-5730
> URL: https://issues.apache.org/jira/browse/SOLR-5730
> Project: Solr
> Issue Type: New Feature
> Reporter: Christine Poerschke
> Assignee: Christine Poerschke
> Priority: Minor
> Attachments: SOLR-5730-part1of2.patch, SOLR-5730-part1of2.patch,
> SOLR-5730-part2of2.patch, SOLR-5730-part2of2.patch
>
>
> *Example configuration (solrconfig.xml):*
> {noformat}
> <sortMerges enable="true">
> <str name="sort">timestamp desc</str>
> </sortMerges>
> {noformat}
> *Example use (EarlyTerminatingSortingCollector):*
> {noformat}
> &sort=timestamp+desc&segmentTerminateEarly=true
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
