Tim,
On 8/25/23 08:23, Tim Funk wrote:
This had been my normal upgrade path now for the major upgrades:
0) Optimistically assume you have all the original data for re-inserts
Check! Everything going into the index also goes into tables in our
RDBMS. Solr is just there to make things go *much* faster, and to allow
decent ranking of results.
1) Copy your config to fresh blank instance
2) Verify your solrconfig.xml has an update to date <luceneMatchVersion>
3) Fix other solrconfig.xml deprecations such as replacing such as
solr.FastLRUCache with solr.CaffeineCache
I would probably create a new Core from scratch, which should take care
of the above. I don't have much in the way of hand-tweaked configuration.
3.5) Fix schema deprecations
4) Populate index (since empty - no delete needed)
4.5) Test - totally optional ;)
Yolo!
5) Cutover core / service to new version
I should look at maybe supporting cut-over in my code. Right now, the
application has a "re-index" capability, but it will re-index to the
same Solr instance/core where the searches are occurring. I could
probably add configuration for a "re-index to this other URL...".
-chris
