Thanks for the detailed description!
On 14.03.2018 16:11, Shawn Heisey wrote:
On 3/14/2018 5:56 AM, Hendrik Haddorp wrote:
So you are saying that we do not need to run the IndexUpgrader tool
if we move from 6 to 7. Will the index be then updated automatically
or will we get a problem once we move to 8?
If you don't run IndexUpgrader, and the index version is one that the
new Solr can read, then existing index segments will remain in the
format they are. New segments will be written in the new format. If
any of the existing segments are merged, then the new larger segment
will be in the new format.
Summary: If an index starts out as 6.x, then is run for a while in
7.x, but there are still 6.x segments left, then that index will not
work in 8.0.
IndexUpgrader is a Lucene tool. This tool just runs a forceMerge
process on the index, which will merge all of the existing segments
into a single segment. It's EXACTLY the same operation that Solr
calls "optimize". (Lucene used to call it optimize too. Then they
renamed it.)
How would one use the IndexUpgrader at all with Solr? Would one need
to run it against the index of every core?
The Solr server must be shut down during the IndexUpgrader run.
IndexUpgrader is a completely separate tool, part of Lucene. It has
zero knowledge of anything that you have configured in Solr, so you
must locate the index directory of any core you want to upgrade and
run the tool on that index directory.
Thanks,
Shawn
