Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Tue, 21 Feb 2006 17:24:58 -0800 (PST)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: java-user@lucene.apache.org
Subject: Re: Open an IndexWriter in parallel with an IndexReader on the same
 index.
In-Reply-To: 
 <OFBC0D871B.E7CC2A41-ONC225711C.0054C492-C225711C.0055B04E@il.ibm.com>
Message-ID: <Pine.LNX.4.58.0602211722050.18041@hal.rescomp.berkeley.edu>
References: 
 <OFBC0D871B.E7CC2A41-ONC225711C.0054C492-C225711C.0055B04E@il.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: It would have been nice if someone wrote something like indexModifier,
: but with a cache, similar to what Yonik suggested above: deletions will
: not be done immediately, but rather cached and later done in batches.
: Of course, batched deletions should not remember the term to delete,
: but rather the matching document numbers at the time of the deletion -
: because after the addition of the modified document if we search for
: the term again we'll find two documents.

That's not a safe sequence of events.  An Add can trigger a segment merge,
which cna renumber documents.

As yonik said, you want to queue up the adds/updates, then do a delete for
each update in your queue, then do your adds in one batch.  knowing
when/what to delete requies knowing a "key" for your records -- which
isnt' a native lucne concept, but it is certainly a general enough one
that a helper class could be written for this.


-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org