Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't close/reopen IndexWriter when changing RAM buffer size #6856

Closed
wants to merge 1 commit into from
Closed

Don't close/reopen IndexWriter when changing RAM buffer size #6856

wants to merge 1 commit into from

Commits on Jul 14, 2014

  1. Core: don't close/reopen IndexWriter when changing RAM buffer size 

    Today we close/reopen IW when we change the RAM buffer but that's
costly because it means the next NRT reader is a full reopen.  The RAM
buffer size setting is a live one in IndexWriter, even if there are no
buffered docs in RAM when you call it.

Separately it would be nice if Lucene let you manage a "reader pool"
that could outlive individual IW instances ...
    @mikemccand
    mikemccand committed Jul 14, 2014
    Copy the full SHA
    31faccb View commit details
    Browse the repository at this point in the history