Michael:
Thanks, that's what I figured, but it's nice to have confirmed.
Erick
On Jan 20, 2008 11:59 AM, Michael McCandless <[EMAIL PROTECTED]>
wrote:
>
> Hi Erick,
>
> Yes, you do still need to guard against this case in 2.3. IndexWriter
> checks the RAM usage after each doc is processed and
Hi Erick,
Yes, you do still need to guard against this case in 2.3. IndexWriter
checks the RAM usage after each doc is processed and flushes when
that's over the limit.
However, the memory consumed by a very large doc should be quite a bit
less than before, because in 2.3 IndexWriter makes mor
About flush by RAM
I was playing around with something similar on the 2.1 codebase
(roll-my-own)
and had the quirk of a possible *very* large incoming document. As in 250M.
So I had to put some logic in to try say, in effect, "if the incoming doc is
completely ridiculous, flush now". I should say
