If you created your index with 7x, you don’t need to do anything, 8x will be
able to operate with it. If you ever used 6x to index any docs you must reindex
completely by deleting the entire index and starting over, or index to a new
collection and use collection aliasing to seamlessly switch.
Hi Team,
Currently I am using Lucene 7.3, I want to upgrade to lucene 8.5.1. Should
I do reindexing in this case ?
Can I make use of backward codec jar without a reindex?
Thanks & Regards,
Adarsh Sunilkumar.
Ah, sorry for the misdirection, thanks for the correction, Erick. That
does jibe with what I now remember having heard before. I guess we
reserve the right to create index data structures in the future for
which we did not save sufficient data in the past.
On Fri, Nov 20, 2020 at 9:15 AM Erick Eri
The IndexUpgraderTool does a forceMerge(1). If you have a large index,
that has its own problems, but will work. The threshold for the issues is
5G. See: https://lucidworks.com/post/solr-and-optimizing-your-index-take-ii/
I should emphasize that if you have a very large single segment as a
result,
I think running the upgrade tool would also be necessary to set you up for
the next upgrade, when 9.0 comes along.
On Fri, Nov 20, 2020, 4:25 AM Uwe Schindler wrote:
> Hi,
>
> > Currently I am using Lucene 7.3, I want to upgrade to lucene 8.5.1.
> Should
> > I do reindexing in this case ?
>
> No
Hi,
> Currently I am using Lucene 7.3, I want to upgrade to lucene 8.5.1. Should
> I do reindexing in this case ?
No, you don't need that.
> Can I make use of backward codec jar without a reindex?
Yes, just add the JAR file to your classpath and it can read the indexes.
Updates written to the
Hi Team,
Currently I am using Lucene 7.3, I want to upgrade to lucene 8.5.1. Should
I do reindexing in this case ?
Can I make use of backward codec jar without a reindex?
Thanks & Regards,
Adarsh Sunilkumar
