Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of trejkaz@trypticon.org
 designates 209.85.220.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPsWd+MzadWW=Pqj1uWr+ZoGsjBrQebtsUc12UowK4jY9C6YZQ@mail.gmail.com>
References: 
 <CADuAvzfEPhQ5dgYiLak5EecCd9dHkhDk+PiSzABdDHmwCygtgA@mail.gmail.com>
	<CAPsWd+MzadWW=Pqj1uWr+ZoGsjBrQebtsUc12UowK4jY9C6YZQ@mail.gmail.com>
Date: Mon, 9 Jun 2014 22:53:59 +1000
Message-ID: 
 <CADuAvzd2EUoM9aPoYyN0Yfw-3R9bZwbut18tMqragbe90u6vCw@mail.gmail.com>
Subject: Re: Reading a v2 index in v4
From: Trejkaz <trejkaz@trypticon.org>
To: Lucene Users Mailing List <java-user@lucene.apache.org>
Content-Type: text/plain; charset=UTF-8

On Mon, Jun 9, 2014 at 10:17 PM, Adrien Grand <jpountz@gmail.com> wrote:
> Hi,
>
> It is not possible to read 2.x indices from Lucene 4, even with a
> custom codec. For instance, Lucene 4 needs to hook into
> SegmentInfos.read to detect old 3.x indices and force the use of the
> Lucene3x codec since these indices don't expose what codec has been
> used to write them.

Rats. I was wondering how the Lucene3x codec worked, but now I know. I
was hoping codecs were going to be more flexible than that, but it
looks like nobody considered the possibility that I might want to pass
a Codec into my IndexReader. :(

TX

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org