lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shay Banon <>
Subject Getting an IndexReader from a committed IndexWriter
Date Fri, 15 May 2009 01:37:10 GMT


   I just had a look at the job done in IndexWriter in order to get an
IndexReader with all the current ongoing changes done using the IndexWriter.
This feature is very useful, and I was wondering if another feature, which
(I think) is simple to implement (compared to the previous one) might make

   Many times, an application opens an IndexWriter, does whatever changes it
does, and then commits the changes. It would be nice to get an IndexReader
(read only one is fine) that corresponds to the committed (or even closed)
IndexWriter. This will allow for a cache of IndexReader that is already used
to be updated with a fresh IndexReader, without the need to reopen one
(which should be slower than opening one based on the IndexWriter
information). The main difference is the fact that the mentioned IndexReader
could still be reopened without the need to throw an AlreadyClosedException.

   Does it make sense?

View this message in context:
Sent from the Lucene - Java Developer mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message