>
Subject: Re: Readers synchronization
To: java-user@lucene.apache.org, [EMAIL PROTECTED]
Date: Tuesday, July 8, 2008, 11:58 AM
No other techniques that I know of...
But there is ongoing discussions/work towards making
reopening a
reader much less costly. EG repopulating the field cache
after
Is there any plan to change this behavior? meaning that by default a reader
will see the current index?
Thanks in advance
--- On Tue, 7/8/08, Michael McCandless <[EMAIL PROTECTED]> wrote:
> From: Michael McCandless <[EMAIL PROTECTED]>
> Subject: Re: Readers synchronizati
e, 7/8/08, Michael McCandless <[EMAIL PROTECTED]>
wrote:
From: Michael McCandless <[EMAIL PROTECTED]>
Subject: Re: Readers synchronization
To: java-user@lucene.apache.org
Date: Tuesday, July 8, 2008, 11:12 AM
No, that's not changed. You must still reopen an
IndexReader to see
> From: Michael McCandless <[EMAIL PROTECTED]>
> Subject: Re: Readers synchronization
> To: java-user@lucene.apache.org
> Date: Tuesday, July 8, 2008, 11:12 AM
> No, that's not changed. You must still reopen an
> IndexReader to see
> changes to the index. An IndexRe
No, that's not changed. You must still reopen an IndexReader to see
changes to the index. An IndexReader always searches a point-in-time
snapshot of the index.
LUCENE-1044 does mean that you should call IndexWriter.commit() (or,
close the writer) to ensure all changes you've made become
According to SVN history on the next version this will be available:
LUCENE-1044: IndexWriter with autoCommit=true now commits (such
that a reader can see the changes) far less often than it used to.
Previously, every flush was also a commit. You can always force a
commit by calling I
