You really should reindex for a 4 version jump. The index upgrader tool
explicitly prohibits what you are proposing to do with it. See
https://issues.apache.org/jira/browse/LUCENE-9127 and
https://solr.apache.org/guide/8_1/indexupgrader-tool.html (It seems that
the javadoc for IndexUpgrader maybe s
Well...
There's a way, but I wouldn't necessarily recommend it.
You can write custom migration code against some version of Lucene
which supports doc values, to create doc values fields. It's going to
involve writing a FilterCodecReader which wraps your real index and
then pretends to also have d
Hi all,
Thank you all for your responses.
So, when updating to a newer (major) Lucene version that modifies its
codecs, there is no way to ensure everything keeps working properly, unless
re-indexing, right?
Apart from not having some original sources that were indexed (which I will
try to solve
Based on what Uwe says, if your problem does relate to shade but you need
to package things in a single executable jar,
https://github.com/nsoft/uno-jar (my fork of the old OneJar utility) might
work better for since it never unpacks any jar file, but instead teaches
java how to treat an overall ja
