You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Rahul Goswami (Jira)" <ji...@apache.org> on 2026/01/31 20:20:00 UTC
[jira] [Updated] (SOLR-18096) Introduce a UPRADECOREINDEX CoreAdmin API to support index upgrade
[ https://issues.apache.org/jira/browse/SOLR-18096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rahul Goswami updated SOLR-18096:
---------------------------------
Description:
Forking this JIRA from parent SOLR-17725 based on [~dsmiley]'s suggestion. The merge policy (LatestVersionMergePolicy) part of the overall enhancement made it into Solr 10 which enables uses to still be able to upgrade their index for the next Solr version (Solr 11), although with more write overhead.
The other part of the enhancement is this JIRA which proposes exposing an UPRADECOREINDEX CoreAdmin API for standalone installations to be able to achieve the upgrade in a highly targeted and efficient way by only upgrading older segments and abstracting the setting of the merge policy.
was:
Forking this JIRA from parent SOLR-1775 based on [~dsmiley]'s suggestion. The merge policy (LatestVersionMergePolicy) part of the overall enhancement made it into Solr 10 which enables uses to still be able to upgrade their index for the next Solr version (Solr 11), although with more write overhead.
The other part of the enhancement is this JIRA which proposes exposing an UPRADECOREINDEX CoreAdmin API for standalone installations to be able to achieve the upgrade in a highly targeted and efficient way by only upgrading older segments and abstracting the setting of the merge policy.
> Introduce a UPRADECOREINDEX CoreAdmin API to support index upgrade
> ------------------------------------------------------------------
>
> Key: SOLR-18096
> URL: https://issues.apache.org/jira/browse/SOLR-18096
> Project: Solr
> Issue Type: Improvement
> Reporter: Rahul Goswami
> Priority: Major
>
> Forking this JIRA from parent SOLR-17725 based on [~dsmiley]'s suggestion. The merge policy (LatestVersionMergePolicy) part of the overall enhancement made it into Solr 10 which enables uses to still be able to upgrade their index for the next Solr version (Solr 11), although with more write overhead.
> The other part of the enhancement is this JIRA which proposes exposing an UPRADECOREINDEX CoreAdmin API for standalone installations to be able to achieve the upgrade in a highly targeted and efficient way by only upgrading older segments and abstracting the setting of the merge policy.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org