lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Cutting <cutt...@apache.org>
Subject Re: Shouldnt IndexWriter.flushRamSegments() be public? or at least protected?
Date Tue, 28 Sep 2004 16:38:41 GMT
Christian Rodriguez wrote:
> Now the problem I have is that I dont have a way to force a flush of
> the IndexWriter without closing it and I need to do that before
> commiting a transaction or I would get random errors. Shouldnt that
> function be public, in case the user wants to force a flush at some
> point that is not when the IndexWriter is closed? If not I am forced
> to create a new IndexWriter and close it EVERY TIME I commit a
> transaction (which in my application is very often).

Opening and closing IndexWriters should be a lightweight operation. 
Have you tried this and found it to be too slow?  A flush() would have 
to do just about the same work.

Doug

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


Mime
View raw message