[
https://issues.apache.org/jira/browse/SOLR-9648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608304#comment-15608304
]
Christine Poerschke commented on SOLR-9648:
-------------------------------------------
bq. ... the implementation doesn't fallback to the delegating merge policy.
Interesting, that is surprising. Created LUCENE-7523 to explore perhaps
changing {{UpgradeIndexMergePolicy}}.
> Wrap all solr merge policies with SolrMergePolicy
> -------------------------------------------------
>
> Key: SOLR-9648
> URL: https://issues.apache.org/jira/browse/SOLR-9648
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Keith Laban
> Attachments: SOLR-9648-WIP.patch
>
>
> Wrap the entry point for all merge policies with a single entry point merge
> policy for more fine grained control over merging with minimal configuration.
> The main benefit will be to allow upgrading of segments on startup when
> lucene version changes. Ideally we can use the same approach for adding and
> removing of doc values when the schema changes and hopefully other index type
> changes such as Trie -> Point types, or even analyzer changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
