lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ning Li" <ning.li...@gmail.com>
Subject Re: [jira] Resolved: (LUCENE-709) [PATCH] Enable application-level management of IndexWriter.ramDirectory size
Date Wed, 22 Nov 2006 20:51:57 GMT
> There is a flaw in this approach as you exceed the threshold before
> flushing.  With very large documents, that can cause an OOM.

This is a good point.

> I agree that it would be better to do this in IndexWriter, but more
> machinery would be needed.  Lucene would need to estimate the size of
> the new ram segment and check the threshold prior to consuming the space.

Agree.

> The API that Yonik committed last night (thanks Yonik!) provides the
> flexibility to address both use cases.  It's a tiny bit more work for

I agree that making flushRamSegments() public provides the
flexibility. I was wondering if there is a way to do a bit more work
so many apps could do less.

Ning

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


Mime
View raw message