[
https://issues.apache.org/jira/browse/SOLR-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119287#comment-15119287
]
Shai Erera commented on SOLR-5730:
----------------------------------
OK I see, then in this issue you want to add another "alongside" attribute for
SortingMP ({{<sortMerges>}}) and then deprecate the whole stuff and move to
MergePolicyFactory? Or did you first intend to introduce MPF, and only then
address SortingMP? I guess that adding {{<sortMerges>}} just to immediately
deprecate it seems odd, especially if both will be released in 5.5...
While we're at it, {{useCompoundFiles}} in Lucene has two meanings too: for
{{IndexWriter}} it determines if flushed segments are flushed as .cfs and in
{{MergePolicy}} it determines about merged segments. The two are not
equivalent, so I suggest we note that in the MPF changes too.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
