On Fri, Aug 2, 2013 at 5:56 PM, Shai Erera wrote:
> Unfortunately you cannot upgrade directly from 2.3.1 to 4.1.
>
> You can consider upgrading to 3.6.2 and stop there. Lucene 4.1 can read 3.x
> indexes, and when segments will are merged, they are upgraded automatically
> to the newest file forma
Unfortunately you cannot upgrade directly from 2.3.1 to 4.1.
You can consider upgrading to 3.6.2 and stop there. Lucene 4.1 can read 3.x
indexes, and when segments will are merged, they are upgraded automatically
to the newest file format.
However, if this single segment is too big, such that it w
Thank you Shai for the quick response. Have responded inline.
On Fri, Aug 2, 2013 at 5:37 PM, Shai Erera wrote:
> Hi
>
> You cannot just update headers -- the file formats have changed. Therefore
> you need to rewrite the index entirely, at least from 2.3.1 to 3.6.2 (for
> 4.1 to be able to rea
Hi
You cannot just update headers -- the file formats have changed. Therefore
you need to rewrite the index entirely, at least from 2.3.1 to 3.6.2 (for
4.1 to be able to read it).
If your index is already optimized, then IndexUpgrader is your best option.
The reason it calls forceMerge(1) is that
Team,
We are migrating from lucene version 2.3.1 to 4.1. We are migrating
the indices as well, and we do this in two steps 2.3.1 to 3.6.2 and 3.6.2
to 4. We just call IndexUpgrader.upgrade(), using the
IndexUpgraderMergePolicy. I see that, the upgrade() method actually calls a
forcemerge(1
