In my experience, you need to index to a new collection, then use the
alias command to point the connection endpoint to the new collection.
Not sure how this works in non-cloud mode.
We've tried reindexing to an existing collection, but, the created
LUCENE version stamp doesn't get updated, and even though the new
segments in theory should be the new LUCENE version, we still could not
go up to the next version. This was when going to 8. We had some indexes
still marked as 6, even though we had fully reindexed to the same
collection and optimized down to a single segment.
On 6/12/22 14:21, Dave wrote:
You don’t need a new core/collection, just reindex everything again. Ideally
since you’re using standalone (way better than cloud imo) you can use the same
indexer, just do an integrity check after the fact to make sure the document
counts are the same. You don’t really need to do that delete if you are just
going to obliterate the previous install and index
On Jun 12, 2022, at 1:49 PM, Christopher Schultz<ch...@christopherschultz.net>
wrote:
All,
We've been using the same major version of Solr for years so haven't had to do
this yet, but we are preparing to upgrade between major versions, now.
After upgrading, I'm assuming that the existing index is "usable" but I've read many
times that "you should reindex after a major version change."
Okay.
Does that just mean:
1. delete *:*
2. re-add all documents
?
Or do we have to create a new core/collection with the schema from scratch and
load it?
I'm using standalone Solr (i.e. no ZK) with a single core if that makes any
difference.
Thanks,
-chris
