You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-user@lucene.apache.org by Ravikumar Govindarajan <ra...@gmail.com> on 2016/06/16 11:18:57 UTC

IndexWriterConfig.readerPooling option...

Came across a JIRA filed for pooling IndexReaders

https://issues.apache.org/jira/browse/LUCENE-2297


For every commit/delete/update cycle IndexWriter opens a bunch of
SegmentReaders, does the job & closes it.

Does the JIRA aim to re-use the SegmentReaders for all commit-cycles till
they are finally closed (after a merge, rollback, iw.close() etc...) ?

Also, we use DirectoryReader.open(dir) construct for searching. Is the
SegmentReader instances associated with this different from that
IndexWriter's & thus have different life-cycle?

Could someone please help in understanding this readerPooling option

--
Ravi