> The problem are not the class names, the problem are the names as
> written to Index. And in a Lucene 4 index there is written e.g., "Lucene47"
> as Codec and Postingsformat. The lookup by name is done by this name.
> IndexReader/Writer does Codec.forName("Lucene47"). For this to work,
> every co
Hi,
> On Mon, Jul 6, 2015 at 4:32 PM, Uwe Schindler wrote:
> > Hi,
> >
> > It could be the reason for this is your classpath:
> >
> > If you load all Lucene Versions into the same classloader (but with
> > different
> package names - I assume you use Maven Shade plugin to do this), Lucene 3
> wi
On Mon, Jul 6, 2015 at 4:32 PM, Uwe Schindler wrote:
> Hi,
>
> It could be the reason for this is your classpath:
>
> If you load all Lucene Versions into the same classloader (but with different
> package names - I assume you use Maven Shade plugin to do this), Lucene 3
> will load perfectly, y
ange package names!
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Trejkaz [mailto:trej...@trypticon.org]
> Sent: Monday, July 06, 2015 5:35 AM
> To: Lucene Users Mailing List
> Subject: Upg
Hi all.
All our existing indices are versions 2 through 3 and we're trying to
migrate everything up to 5 (and then later graft additional DocValues
in, but that's the next step.)
I wrote a tool which basically does this:
public void upgrade2to5(Path path, int currentVersion) {
if (cu
