Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of torindan@gmail.com designates
 74.125.83.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEY5pxUJoNqpgqzsg909PA0X_h9-fNnN0iwzfo+p=uU2GX-B7g@mail.gmail.com>
References: 
 <CAPzrt-0CJeC2=RHaLs0BjBD95xeAPQZ9Zoftc+E+q=CFC2=1Cg@mail.gmail.com>
 <CAEY5pxUJoNqpgqzsg909PA0X_h9-fNnN0iwzfo+p=uU2GX-B7g@mail.gmail.com>
From: =?UTF-8?B?RGFuaWwgxaJPUklO?= <torindan@gmail.com>
Date: Tue, 20 Nov 2012 12:24:38 +0200
Message-ID: 
 <CABYvkPQfbHVr2FLozzL00ZTcL9kzFVDBz4qMSyBnQJaJW=fn_Q@mail.gmail.com>
Subject: Re: Using Lucene 2.3 indices with Lucene 4.0
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=047d7b3a7ff885383404ceeaa618

--047d7b3a7ff885383404ceeaa618
Content-Type: text/plain; charset=UTF-8

However behavior of some analyzers changed.

So even after upgrade the old index is readable with 4.0, it doesn't mean
everything still works as before.

On Tue, Nov 20, 2012 at 12:20 PM, Ian Lea <ian.lea@gmail.com> wrote:

> You can upgrade the indexes with org.apache.lucene.index.IndexUpgrader.
>  You'll need to do it in steps, from 2.x to 3.x to 4.x, but should work
> fine as far as I know.
>
>
> --
> Ian.
>
>
>
> On Tue, Nov 20, 2012 at 10:16 AM, Ramprakash Ramamoorthy <
> youngestachiever@gmail.com> wrote:
>
> > I understand lucene 2.x indexes are not compatible with the latest
> version
> > of lucene 4.0. However we have all our indexes indexed with lucene 2.3.
> >
> > Now that we are planning to migrate to Lucene 4.0, is there any work
> > around/hack I can do, so that I can still read the 2.3 indices? Or is
> > forgoing the older indices the only option?
> >
> > P.S : Am afraid, Re-indexing is not feasible.
> >
> > --
> > With Thanks and Regards,
> > Ramprakash Ramamoorthy,
> > Chennai,
> > India.
> >
>

--047d7b3a7ff885383404ceeaa618--