il: u...@thetaphi.de
> -Original Message-
> From: Trejkaz [mailto:trej...@trypticon.org]
> Sent: Monday, June 09, 2014 2:54 PM
> To: Lucene Users Mailing List
> Subject: Re: Reading a v2 index in v4
>
> On Mon, Jun 9, 2014 at 10:17 PM, Adrien Grand
> wrote:
&g
On Mon, Jun 9, 2014 at 10:17 PM, Adrien Grand 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
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.
On Mon, Jun 9
Hi all.
The inability to read people's existing indexes is essentially the
only thing stopping us upgrading to v4, so we're stuck indefinitely on
v3.6 until we find a way around this issue.
As I understand it, Lucene 4 added the notion of codecs which can
precisely choose how to read and write th
