lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jake Mannix <jake.man...@gmail.com>
Subject Re: Realtime search best practices
Date Mon, 12 Oct 2009 19:38:57 GMT
On Mon, Oct 12, 2009 at 12:26 PM, Michael McCandless <
lucene@mikemccandless.com> wrote:

> On Mon, Oct 12, 2009 at 3:17 PM, Jake Mannix <jake.mannix@gmail.com>
> wrote:
>
> > Wait, so according to the javadocs, the IndexReader which you got from
> > the IndexWriter forwards calls to reopen() back to
> IndexWriter.getReader(),
> > which means that if the user has a NRT reader, and the user keeps calling
> > reopen() on it, they're getting uncommitted changes as well, while if
> they
> > call reopen() on a regular IndexReader, they do not?
>
> That's right.
>

So maybe since it's an "expert" feature, this is ok, but if users are used
to using
isCurrent() on their reader instances, this seems like it might get
confusing, since
now some readers are even more current than current, and in fact the NRT
readers may be current w.r.t. the most recent commit, but calling reopen()
on
them will actually still make them more current, in that they now get a view
on even more recent uncommitted changes...

  -jake

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