Jason Gerlowski commented on SOLR-11229:

Hey [~hgadre], took a quick look at the tool you mentioned above.  Had a few 

- I noticed that the TODO list in the README.md doesn't mention anything about 
Windows support.  Is a Windows version of this script in the scope of this 
JIRA?  Or is the idea that it'd be added as a part of a separate JIRA later on?
- I'm curious about the choice of XSLT here.  XSLT isn't rocket science, but it 
does have its traps, and it's another thing maintainers (and users) will have 
to dig into.  At a quick glance, much of the XSLT logic could also be done with 
xpath (in bash, or invoked from Java-land)...though it's totally possible I 
missed something.  Did you consider the maintenance tradeoff between XSLT and 
Java?  Or the test-ability tradeoff?  Or is there maybe a reason I'm missing 
that makes XSLT required?
- I notice that 
 mimics but doesnt technically implement the Solr 
 interface.  Is the idea that as this makes its way into Solr, it would 
actually implement that interface?  Or is it coincidence that those classes 
look similar.  This is not a suggestion or a critique; just trying to 
understand the code a little better.

> 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

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

Reply via email to