How we would do it:
- update the index format to v7 (this in itself is fiddly
but there are ways)
- open the index in-place migrated:
- get all the leaf indices and wrap each in a new
subclass of FilterCodecReader
- override getPointsReader() on that subclass
to return a
Ok,
I know this policy and you perfectly explained why it makes sense.
Anyway my index is really big and contains mostly textual data which are
expensive to reindex (because of custom analysis).
Considering that the IndexUpgrader will efficiently do the most of the work
I should investigate how
You cannot upgrade more than one major version, you must re-index from scratch.
There’s a long discussion of why, but basically it’s summed up by this quote
from Robert Muir:
“I think the key issue here is Lucene is an index not a database. Because it is
a lossy index and does not retain all
Hello everybody,
I have a (very big) lucene 4 index with documents using IntField. On that
field, which should be stored and sortable, I should search and execute
range queries.
I've tried to upgrade it from 4 to 7 with IndexUpgrader but I observed that
IntFields aren't searchable anymore.
4 June 2019, Apache Lucene™ 7.7.2 available
The Lucene PMC is pleased to announce the release of Apache Lucene 7.7.2.
Apache Lucene is a high-performance, full-featured text search engine library
written entirely in Java. It is a technology suitable for nearly any
application that requires
