[
https://issues.apache.org/jira/browse/SOLR-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126694#comment-15126694
]
Hoss Man commented on SOLR-8621:
--------------------------------
bq. (proposed) roadmap:
A pattern we've followed in the past is to make those deprecations/failures
contingent on luceneMatchVersion.
So a person using Solr X >= 5.5 with a luceneMatchVersion < 5.5 gets a warning
that mergePolicy is deprecated. but if they change their luceneMatchVersion >=
5.5 then it starts being an error.
That way users who do a drop in upgrade w/o changing configs just get a handy
warning, but new users who start with an example config that has
luceneMatchVersion >= 5.5 will get a helpful fail-fast error if they try to
follow old advice/docs and add something that's already dperecated.
(most of the places you see {{assertWarnOrFail(..., true)}} used use to have a
luceneMatchVersion comparison done in the last param, before those very old
version constants (ie pre 5.0) were completely removed)
> 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]