Besides the warm up that the faq section suggests (used on solr), is there
another technique or solution to have an IndexReader/Search with an updated
view of an index under a concurrent scenario (web app)?
Thanks
--- On Tue, 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
> 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 visible to
> the reader.
>
> Mike
>
> Eric Diaz wrote:
>
> > 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 IndexWriter.commit().
> Furthermore, in 3.0,
> > autoCommit will be hardwired to false (IndexWriter
> constructors
> > that take an autoCommit argument have been
> deprecated) (Mike
> > McCandless)
> >
> > Does this mean that I won't need to reopen all the
> readers in order
> > to see the index changes?
> >
> > Thanks
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail:
> [EMAIL PROTECTED]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
