lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ravikumar Govindarajan <>
Subject IndexWriterConfig.readerPooling option...
Date Thu, 16 Jun 2016 11:18:57 GMT
Came across a JIRA filed for pooling IndexReaders

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 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


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message