Hi,
> > > The first time my code used the 3.4 libraries with version level set
> > > to 3.4 and it tried to optimize() (still using this now deprecated
> > > old call), the new code
> > went wild!
> > > It took up more memory than the heap was limited to, so I believe it
> > > is taking
> > > up s
Thanks for the reply,
> > The first time my code used the 3.4 libraries with version level set
> > to 3.4 and it tried
> > to optimize() (still using this now deprecated old call), the new code
> went wild!
> > It took up more memory than the heap was limited to, so I believe it
> > is taking
> >
Hi,
> After reading all about the renaming of optimize() and updating my Lucene
> libraries to 3.4, I was surprised and confused by what I found.
>
> I have a 1 segment index (all files are named _1*.*) that had been
created
> with 3.0.1 code which had been optimized many times (all 3.0.1 code)
After reading all about the renaming of optimize() and updating my Lucene
libraries to 3.4, I was surprised and confused by what I found.
I have a 1 segment index (all files are named _1*.*) that had been created
with 3.0.1 code which had been optimized many times (all 3.0.1 code). The
first
