lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kelvin Tan" <kel...@relevanz.com>
Subject Re: Indexing and Searching happening together
Date Fri, 01 Feb 2002 10:00:40 GMT
hmmmm...have read http://www.mail-archive.com/lucene-user@jakarta.apache.org/msg00133.html

True (and it's great) that once an IndexReader is open, no actions on the IndexWriter affect
it. 

However, if an IndexReader is opened _after_ indexing begins, I suppose it'll throw an exception?
Doesn't it mean that when indexing is taking place, the search engine is effectively down...

I suppose then, that if I still want to have the search engine up whilst indexing (where indexing
takes a non-trivial amount of time), I'll have to index to a temporary location, then copy
the index files over? Alternatively, I guess it's possible to open an IndexReader _before_
commencement of indexing and provide this instance of IndexReader to clients who need to search?

I just realized that I've effectively rephrased my initial question (and post). Perhaps it's
the way I phrased my question (or that I'm missing something), but I don't seem to have gotten
my query across initially...

Regards,
Kelvin
  ----- Original Message ----- 
  From: Doug Cutting 
  To: 'Lucene Users List' 
  Sent: Friday, February 01, 2002 12:28 AM
  Subject: RE: Indexing and Searching happening together


  > From: Kelvin Tan [mailto:kelvin@relevanz.com]
  > 
  > In the case where indexing takes a non-trivial amount of 
  > time, what is the expected behaviour when a search is 
  > performed while indexing is still going on? 

  Once an IndexReader is open, no actions on an IndexWriter should affect it.
  Adding documents in another thread or process will not affect search results
  until a new IndexReader is opened.  Searching and indexing may proceed
  simultaneously.

  Doug

  --
  To unsubscribe, e-mail:   <mailto:lucene-user-unsubscribe@jakarta.apache.org>
  For additional commands, e-mail: <mailto:lucene-user-help@jakarta.apache.org>



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