[
https://issues.apache.org/jira/browse/SOLR-9648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132112#comment-18132112
]
Nick Shanin commented on SOLR-9648:
-----------------------------------
>From code reading against apache/main b73f03976fa, segment upgrading exists
>only as the opt-in UpgradeIndexMergePolicyFactory
>(solr/core/src/java/org/apache/solr/index/UpgradeIndexMergePolicyFactory.java:25-34),
> and nothing upgrades segments on startup. Is automatic startup upgrade still
>wanted, or is the opt-in factory enough to close this?
🤖 AI-generated 🤖
> Wrap all solr merge policies with SolrMergePolicy
> -------------------------------------------------
>
> Key: SOLR-9648
> URL: https://issues.apache.org/jira/browse/SOLR-9648
> Project: Solr
> Issue Type: Bug
> Reporter: Keith Laban
> Priority: Major
> 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
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
