lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hrishikesh Gadre (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-11229) Add a configuration upgrade tool for Solr
Date Fri, 11 Aug 2017 20:18:01 GMT

    [ https://issues.apache.org/jira/browse/SOLR-11229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123975#comment-16123975
] 

Hrishikesh Gadre commented on SOLR-11229:
-----------------------------------------

The initial prototype of this tool is available @ https://github.com/hgadre/solr-upgrade-tool

> Add a configuration upgrade tool for Solr
> -----------------------------------------
>
>                 Key: SOLR-11229
>                 URL: https://issues.apache.org/jira/browse/SOLR-11229
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 6.6
>            Reporter: Hrishikesh Gadre
>
> Despite widespread enterprise adoption, Solr lacks automated upgrade tooling. It has
long been a challenge for users to understand the implications of a Solr upgrade. Users must
manually review the Solr release notes to identify configuration changes either to fix backwards
incompatibilities or to utilize latest features in the new version. Additionally, users must
identify a way to migrate existing index data to the new version (either via an index upgrade
or re-indexing the raw data).
> Solr config upgrade tool aims to simplify the upgrade process by providing upgrade instructions
tailored to your configuration. These instructions can help you to answer following questions
> - Does my Solr configuration have any backwards incompatible sections? If yes which ones?
> - For each of the incompatibility - what do I need to do to fix this incompatibility?
Where can I get more information about why this incompatibility was introduced (e.g. references
to Lucene/Solr jiras)?
> - Are there any changes in Lucene/Solr which would require me to do a full reindexing
OR can I get away with an index upgrade?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message