+1. Support for transactions in Lucene are high on my list of desirable features as well. I would love to have time to look into adding this, but lately... well, you know how that goes.

Scott

Eric Jain wrote:
If you want to update a set of documents, you can remove their previous
version first and then add them after that. In the mean time documents
of this set are temporaly not available. If you have to update a single
document and make the changes immediately public, I don't know a better
solution than yours.

Thanks. I'm not so much worried about temporary inconsistencies as the index
is maintained separately. Of course it would be great if Lucene provided
direct support for some kind of transactional integrity! Anyways, removing
all changed documents first means I have to scan through all documents
twice, not very efficient, though in fact faster than the procedure I
described.


--
Eric Jain


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
Brain: Pinky, are you pondering what I�m pondering?
Pinky: I think so, Brain, but calling it a pu-pu platter? Huh, what were they thinking?


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to