[
https://issues.apache.org/jira/browse/SOLR-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127869#comment-15127869
]
Shai Erera commented on SOLR-8621:
----------------------------------
bq. Will both the <mergeFactor> and <maxMergeDocs> elements will be deprecated
as well
Yes
{quote}
IIUC, the motivation here is to permit any number of merge policies to be
configured with the goal of supporting wrapping of merge policies. Okay, but
what tells Solr which MP is the outer/default MP?
{quote}
The intention is to have a {{MergePolicyFactory}} which creates a
{{MergePolicy}} instance. See [~cpoerschke] description above for the proposed
structure in {{solrconfig.xml}}. If you want to construct your own MP, maybe
it's a compound MP, you can simply define the class name of your factory, and
then pass whatever arguments inside.
> solrconfig.xml: deprecate/replace <mergePolicy> with <mergePolicyFactory>
> -------------------------------------------------------------------------
>
> Key: SOLR-8621
> URL: https://issues.apache.org/jira/browse/SOLR-8621
> Project: Solr
> Issue Type: Task
> Reporter: Christine Poerschke
> Assignee: Christine Poerschke
>
> *<mergePolicyFactory> end-user benefits:*
> * Lucene's UpgradeIndexMergePolicy can be configured in Solr
> * (with SOLR-5730) Lucene's SortingMergePolicy can be configured in Solr
> * customisability: arbitrary merge policies including wrapping/nested merge
> policies can be created and configured
> *(proposed) roadmap:*
> * solr 5.5 introduces <mergePolicyFactory> support
> * solr 5.5(\?) deprecates (but maintains) <mergePolicy> support
> * solr 6.0(\?) removes <mergePolicy> support
> +work-in-progress git branch:+
> [master-solr-8621|https://github.com/apache/lucene-solr/tree/master-solr-8621]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
