Newly added docs are still free to make new segments, and be reopened, while this warming is taking place.
So, getReader() will wait for newly added/deleted docs to be flushed & reopened, but will not wait for any running merges to complete (finish writing the files & finish warming a SegmentReader on the resulting merged segment). Mike On Thu, May 28, 2009 at 3:57 PM, Yonik Seeley <yo...@lucidimagination.com> wrote: > On Thu, May 28, 2009 at 3:30 PM, Michael McCandless > <luc...@mikemccandless.com> wrote: >> This is exactly why we added IndexReaderWarmer -- it pre-warms a newly >> merged segment before committing to SegmentInfos. >> >> So, while such warming is happening, if getReader() is called, the >> returned reader will still read the old segments. > > I don't see how this helps turnaround time from document addition to > making it searchable. > > Using the old reader until the new one is "ready" (however that's > defined) can easily be done at the application level (like Solr and > others do it). It seems like getReader() should block until it can > return a reader containing all of the documents previously added... > that gives the most power to the application. > > -Yonik > http://www.lucidimagination.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
