[
https://issues.apache.org/jira/browse/SOLR-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christine Poerschke updated SOLR-8668:
--------------------------------------
Attachment: SOLR-8668-part1.patch
bq. ... I think a warning might be a fair compromise, instead of an exception
or silent ignoring.
I like that compromise idea, thanks for suggesting it!
Attaching SOLR-8668-part1.patch (ready for review) to correspond to the current
https://github.com/apache/lucene-solr/tree/jira/solr-8668 working branch diff
against master.
Planning to make this ticket's changes in two parts:
* part 1: the bulk of the changes (includes throwing exception if <mergePolicy>
is still configured)
* part 2: small incremental change (replace throwing-exception with log-warning)
The two part split is so that tests very obviously break if they inadvertently
still use <mergePolicy>.
> Remove support for <mergePolicy> (in favour of <mergePolicyFactory>)
> --------------------------------------------------------------------
>
> Key: SOLR-8668
> URL: https://issues.apache.org/jira/browse/SOLR-8668
> Project: Solr
> Issue Type: Improvement
> Reporter: Shai Erera
> Priority: Blocker
> Fix For: master (7.0)
>
> Attachments: SOLR-8668-part1.patch
>
>
> Following SOLR-8621, we should remove support for {{<mergePolicy>}} (and
> related {{<mergeFactor>}} and {{<maxMergeDocs>}}) in trunk/6x.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
