lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Rutherglen" <>
Subject Re: IndexReaderWriter
Date Thu, 21 Aug 2008 13:47:09 GMT

The realtime search code is more or less ready.  It probably needs some more
test cases related to multithreading.  I could use some help in coming up
with test cases as admittedly I struggle with them.

In terms of the native Lucene version, I think it may be useful to offer
optimistic concurrency which would make the API slightly different than
IndexWriter's add, delete, update document methods.  The reason optimistic
concurrency is needed is updating documents can become problematic without
it in realtime.

The API might look something like:
updateDocument(String id, long version, Document document)
deleteDocument(String id)

On Thu, Aug 21, 2008 at 5:42 AM, Michael McCandless <> wrote:

> I agree: getting real-time search working natively in Lucene is an
> important goal.
> I think as an immediate step we should get Ocean committed in contrib?
> This way users can easily try it out, report back, etc.
> Ocean is nice in that it operates above Lucene's core (using
> InstantiatedIndex/Reader to handle the "live" additions).  Besides
> LUCENE-1314 (forcing IndexReader.reopen to return a clone even when no
> changes have been committed to the index), are there any other pending
> core changes that Ocean needs?
> Mike
> Jason Rutherglen wrote:
>  Hello all,
>> Michael McCandless and Yonik Seeley and I were discussing the
>> IndexReaderWriter which would be a combined IndexReader and IndexWriter
>> class.  The name of the class can change.  One key feature that can be added
>> is realtime search.  Realtime search would enable Lucene to have database
>> like functionality whereby each update is immediately searchable as opposed
>> to today where each update is searchable after a commit.  The Ocean code
>> implements realtime search and could provide the basis for this
>> functionality.  I would like to get to an agreement on the scope and
>> functionality of the project and gather input.
>> Thanks!
>> Jason Rutherglen
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message