If that is the case, then I think it is far easier and efficient to
use OID's to track which documents should be deleted, and which
should be added at commit time.
It seems that people using 'transactional' code probably have OIDs.
Then you just created an ordered list of operations (delete OID A,
insert document B (which always deleted B's OID first), insert
document D), etc.
It is easy to write this to a tx log file as the requests come in,
and then play back until it completes.
This also puts you in a better position to use the KS sort pool
model, and perform a single segment write.
On Jan 17, 2007, at 2:11 PM, Marvin Humphrey wrote:
On Jan 17, 2007, at 12:00 PM, robert engels wrote:
Under this new scenario, what is the result of this:
I open the IndexWriter.
I delete all documents with Term A.
I add a new document with Term A.
I delete all documents with Term A.
Is the new document correctly removed?
Not in KS right now.
Hmm.
I think what you'd have to do is save all the terms, then run a
deletion op against the new segment after it's written.
Marvin Humphrey
Rectangular Research
http://www.rectangular.com/
---------------------------------------------------------------------
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]
