[jira] [Updated] (SOLR-9648) Wrap all solr merge policies with SolrMergePolicy

["Keith Laban (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-9648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Laban updated SOLR-9648:
------------------------------
    Attachment: SOLR-9648-WIP.patch

Adding a naive implementation that will upgrade of segments on startup (no tests). As of now this doesn't allow any configuration options to be passed, but can be easily added.

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org