Hendrik:
There's one problem with IndexUpgraderTool. As Shawn points out, it
does a forceMerge, which by default creates one large segment. This
has some implications in terms of the number of deleted documents if
the index has updates afterwards, see:
https://lucidworks.com/2017/10/13/segment-me
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 m
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 th
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?
How would one use the IndexUpgrader at all with Solr? Would one need to
run it against the index of every core?
On 3/14/2018 3:04 AM, Hendrik Haddorp wrote:
we have a SolrCloud 6.3 with HDFS setup and plan to upgrade to 7.2.1.
The cluster upgrade instructions on
https://lucene.apache.org/solr/guide/7_2/upgrading-a-solr-cluster.html
does not contain any information on changing the luceneMatchVersion.
If
Hi,
we have a SolrCloud 6.3 with HDFS setup and plan to upgrade to 7.2.1.
The cluster upgrade instructions on
https://lucene.apache.org/solr/guide/7_2/upgrading-a-solr-cluster.html
does not contain any information on changing the luceneMatchVersion. If
we change the luceneMatchVersion manuall